Sat, 25 Aug 2001 15:58:37 -0400 (EDT)
> So here's a thought. The term "REpresentational State Transfer" is
> broadly suggestive of a general technique that's not specific to HTTP.
> Roy coined the term to specifically refer to the architecture of "the Web"
> --- whatever that means, does that mean anything I can refer to with a URI
> --- but in use it seems pretty tightly-bound to HTTP.
> I don't think there's any harm in thinking about modeling things in the
> style and semantics of HTTP, but using other transports. Perhaps we need
> a more generic term for REST-in-the-abstract vs. REST-bound-to-HTTP.
Excellent point. I'd been thinking about this too.
Are HTTP's method semantics part of REST or not?
I've started a Wiki page on this;