Originally posted by ankur rathi:
What exactly is REST??? Isn't it sending XML over HTTP?
Originally posted by Peer Reynders:
REST requires that you organize your design around "resources", each of which has its own URI. Then you use the standard HTTP methods to obtain or manipulate the "state" of those resources. This is accomplished through the exchange of "representations". The "representations" can be in an XML format but they don't have to be - as a matter of fact the same resource may be capable of "representing its state" in multiple formats and give you the preferred format that you specified in the Accept HTTP header.
State of the resource - what is it? Say, I have an image on server which is a resource, what states it cab be in???
Originally posted by ankur rathi:
State of the resource - what is it? Say, I have an image on server which is a resource, what states it cab be in???
Originally posted by William Brogden:
All the possible images - a very large number indeed.
Bill
Originally posted by Peer Reynders:
So in essence the (camera) resource identified by that URI changes its state approximately every 4 minutes and the representation of that state is an image stored in the JPEG format.
Originally posted by ankur rathi:
Okay, but they are different resources not the different states of a resource.
How different it (REST) is from sending image over http (<img src="a.jpg" />) in the sense of implementation???
Okay, but they are different resources not the different states of a resource.
Originally posted by ankur rathi:
Okay, but they are different resources not the different states of a resource.
Originally posted by Ulf Dittmer:
The resource here is the camera, not the image.
Originally posted by William Brogden:
The URI defines a resource - the data at the other end can change.
That is the whole point of REST - admittedly hard to grasp if you are used to thinking the other way around. See that Tim Ewald blog that Peer cites above.
Bill
Someone is updating the pic. What's REST in it?
Originally posted by ankur rathi:
URI is same all the time but different-different resource might come up to the client (in other word, a different state).
In either case, the state of the client will change... and it will keep on changing as client accesses resources.
Originally posted by ankur rathi:
I am reading but not understanding much.
Yeah, but how did the squirrel get in there? Was it because of the tiny ad?
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|