锘??xml version="1.0" encoding="utf-8" standalone="yes"?>一区二区三区在线影院,日韩一二三四区,成人h动漫免费观看网站http://www.aygfsteel.com/honzeland/category/43479.html璁板綍鐐規淮銆傘傘?/description>zh-cnFri, 08 Jan 2010 07:06:36 GMTFri, 08 Jan 2010 07:06:36 GMT60Web application design: the REST of the storyhttp://www.aygfsteel.com/honzeland/archive/2010/01/08/308718.htmlhonzelandhonzelandFri, 08 Jan 2010 06:50:00 GMThttp://www.aygfsteel.com/honzeland/archive/2010/01/08/308718.htmlhttp://www.aygfsteel.com/honzeland/comments/308718.htmlhttp://www.aygfsteel.com/honzeland/archive/2010/01/08/308718.html#Feedback0http://www.aygfsteel.com/honzeland/comments/commentRss/308718.htmlhttp://www.aygfsteel.com/honzeland/services/trackbacks/308718.htmlWeb application design: the REST of the story
Key points:
HTTP is a very general, scalable protocol. While most people only
think of HTTP as including the GET and POST methods used by typical
interactive browsers, HTTP actually defines several other methods that
can be used to manipulate resources in a properly designed application
(PUT and DELETE, for instance). The HTTP methods provide the verbs in a web interaction.
Servers are completely stateless. Everything necessary to service a request is included by the client in the request.
All application resources are described by unique URIs. Performing
a GET on a given URI returns a representation of that resource's state
(typically an HTML page, but possibly something else like XML). The
state of a resource is changed by performing a POST or PUT to the
resource URI. Thus, URIs name the nouns in a web interaction.