<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Web, Technologies, IA, Vidéo... - Analyse, Développement web, SOA</title><link href="https://www.alkannoide.com/" rel="alternate"/><link href="https://www.alkannoide.com/feeds/analyse-developpement-web-soa.atom.xml" rel="self"/><id>https://www.alkannoide.com/</id><updated>2013-03-08T10:53:00+01:00</updated><entry><title>REST cookbook</title><link href="https://www.alkannoide.com/2013/03/08/rest-cookbook/" rel="alternate"/><published>2013-03-08T10:53:00+01:00</published><updated>2013-03-08T10:53:00+01:00</updated><author><name>admin</name></author><id>tag:www.alkannoide.com,2013-03-08:/2013/03/08/rest-cookbook/</id><summary type="html">&lt;p&gt;A new small blog post where I sticked informations or links about &lt;a href="http://en.wikipedia.org/wiki/Representational_State_Transfer"&gt;Rest&lt;/a&gt; and &lt;a href="http://en.wikipedia.org/wiki/Representational_State_Transfer"&gt;Restful&lt;/a&gt; :a style of architecture for distributed softwares. This post will be updated each time I have new links.&lt;/p&gt;
&lt;p&gt;Restful is stateless. The main goals of Restful architecture are scalability, availability and agnotiscs technologies between software …&lt;/p&gt;</summary><content type="html">&lt;p&gt;A new small blog post where I sticked informations or links about &lt;a href="http://en.wikipedia.org/wiki/Representational_State_Transfer"&gt;Rest&lt;/a&gt; and &lt;a href="http://en.wikipedia.org/wiki/Representational_State_Transfer"&gt;Restful&lt;/a&gt; :a style of architecture for distributed softwares. This post will be updated each time I have new links.&lt;/p&gt;
&lt;p&gt;Restful is stateless. The main goals of Restful architecture are scalability, availability and agnotiscs technologies between software (via an common interface). A new Internet draft is out, it names &lt;a href="http://tools.ietf.org/html/draft-williams-http-rest-auth-00"&gt;RESTful Authentication Pattern&lt;/a&gt; and will help to design your architecture.&lt;/p&gt;
&lt;p&gt;If you will deploy this type of architecture, you can read this slideshare which give &lt;a href="http://blog.apigee.com/detail/slides_for_restful_api_design_second_edition_webinar/"&gt;best practices to design API&lt;/a&gt; (a webinar is available too). To design a Restful architecture, you need to &lt;a href="http://redrata.com/restful-uri-design/"&gt;design your URI&lt;/a&gt;. There is another good document made by &lt;a href="http://www.apigee.com"&gt;Apigee&lt;/a&gt; : &lt;a href="http://info.apigee.com/Portals/62317/docs/web%20api.pdf"&gt;Web API Design&lt;/a&gt; - Crafting interfaces that Developers love [PDF file]&lt;/p&gt;
&lt;p&gt;Here is some examples of API architectures:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span style="line-height: 16px;"&gt;&lt;a href="http://techblog.netflix.com/2013/01/optimizing-netflix-api.html"&gt;Optimizing the Netflix API&lt;/a&gt;&lt;br&gt;
  &lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To conclude, there is a tool to assist you on your development : &lt;a href="http://code.google.com/p/rest-client/"&gt;Rest-client&lt;/a&gt;. It's a Java app (so cross-platform) to test your Restful webservices.&lt;/p&gt;</content><category term="Analyse, Développement web, SOA"/><category term="api"/><category term="rest"/><category term="soa"/></entry></feed>