On Nov 30, 2006, at 8:03 AM, Steve Jones wrote:
So "graph" isn't a resource? But "GraphId452354" would be? I have to say in my reading of REST so far its the former that I've understood (and sometimes liked) while the later would just be rubbish as you'd have one resource per object instance (i.e. you are arguing that REST is on objects, my reading of the subject was that it was on classes).
That's the misunderstanding, then: REST indeed uses URIs (at least in general and conceptually) to identify objects (instances), not classes, via URIs.
For example, if your "application" (to avoid the term service) manages customers, you'd very likely have a distinct URI for every customer (in REST) as opposed to a single endpoint for the CustomerManagementService (which is the common WSDL/SOAL/WS-* approach).
Stefan -- Stefan Tilkov, http://www.innoq.com/blog/st/
smime.p7s
Description: S/MIME cryptographic signature
