REST describes ways of using HTTP that are polite and scalable, from an internet-wide infrastructure perspective.
An analogy is politeness/civility patterns in human language. Some human language constructs may solve the same problem: "Give me the milk!" vs "Please pass the milk" One is more polite than the other. In the context of civil/cooperative human society, the polite utterance is going to be more successful. A lot about how browsers work and how people make web sites is "RESTful" by default/accident. REST and current HTTP co-evolved, with REST serving as the architecture and HTTP as the implementation (roughly speaking). A blunt example of a non-RESTful use would be a site that does write operations with HTTP GET- http://site.com/saveSomeData?key=foo&value=bar http://site.com/getSomeData?key=foo -> returns bar On Fri, Aug 13, 2010 at 1:47 AM, sic <[email protected]> wrote: > I hope to understand not the restlet but the concept of REST itself, sorry > for that. > > What's the meaning of the REST compared with HTTP using commonly all around > the world? > > Easily, we can already access any data via HTTP web browser and get data > from them. > > through the HTTP protocol, it is already possible to take some resources > from somewhere, which is the new main architecture of REST, so irony. > > Even though I try to read some documents and toturial related to the REST > and consider them deeply, It's so hard for me to find out the meaning of the > REST. > > Can anyone give me some advice for that whatever you know? > > regards, > sic > -- > View this message in context: > http://restlet-discuss.1400322.n2.nabble.com/concept-of-REST-and-HTTP-itself-tp5418942p5418942.html > Sent from the Restlet Discuss mailing list archive at Nabble.com. > > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2646260 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2646515
