Geeks With Blogs
Realizing Results my personal notes on C#, SharePoint and object oriented programming
Lets have a look what is REST?
REST (Representational State Transfer)- An Architectural Style, Not a Standard
REST is not a standard. You will not see the W3C putting out a REST specification. You will not see IBM or Microsoft or Sun selling a REST developer's toolkit. Why? Because REST is just an architectural style. You can't bottle up that style. You can only understand it, and design your Web services in that style. (Analogous to the client-server architectural style. There is no client-server standard.)
While REST is not a standard, it does use standards:
·         HTTP
·         URL
·         XML/HTML/GIF/JPEG/etc (Resource Representations)
·         text/xml, text/html, image/gif, image/jpeg, etc (MIME Types)
Principles of REST Web Service Design
·         1. The key to creating Web Services in a REST network (i.e., the Web) is to identify all of the conceptual entities that you wish to expose as services. Above we saw some examples of resources: parts list, detailed part data, purchase order.
·         2. Create a URL to each resource. The resources should be nouns, not verbs. For example, do not use this:
·         Note the verb, get Part. Instead, use a noun:
·         3. Categorize your resources according to whether clients can just receive a representation of the resource, or whether clients can modify (add to) the resource. For the former, make those resources accessible using an HTTP GET. For the later, make those resources accessible using HTTP POST, PUT, and/or DELETE.
·         4. All resources accessible via HTTP GET should be side-effect free. That is, the resource should just return a representation of the resource. Invoking the resource should not result in modifying the resource.
·         5. No man/woman is an island. Likewise, no representation should be an island. In other words, put hyperlinks within resource representations to enable clients to drill down for more information, and/or to obtain related information.
·         6. Design to reveal data gradually. Don't reveal everything in a single response document. Provide hyperlinks to obtain more details.
·         7. Specify the format of response data using a schema (DTD, W3C Schema, RelaxNG, or Schematron). For those services that require a POST or PUT to it, also provide a schema to specify the format of the response.
·         8. Describe how your services are to be invoked using either a WSDL document, or simply an HTML document.
 
For more information checkout this link:-
 
Posted on Friday, October 29, 2010 2:15 PM | Back to top


Comments on this post: REST - Representational State Transfer

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Manish Sati | Powered by: GeeksWithBlogs.net