And then everything inherits from that Resource, got that, but the argument
on class v instance remains. If an invocation creates a new instance then
graph is fine, if however an end point = instance then they'd have to be
uniquely identified.
The later would be rubbish.
On 30/11/06, algermissen1971 <[EMAIL PROTECTED]> 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).
>>
It is really as simple as this:
class Resource
{
public string URI;
public Response GET();
public Response PUT( byte[] data );
public Response POST( byte[] data );
public Response DELETE();
}
It is like an ordinary OO system, just that there is only a single
class, object pointers (or refs) are globally unique and the runtime
is ubiquitous (if you happen to have an ethernet cable).
Jan
