[
Lists Home |
Date Index |
Thread Index
]
Gavin Thomas Nicol wrote:
>
> On Tuesday 12 February 2002 01:06 pm, Mark Baker wrote:
> > Thought why he wouldn't want it to identify himself, rather than an
> > HTML page is a different question. Certainly just *because* the GET
> > returns an HTML when you ask it for that (all browsers ask for
> > text/html), doesn't mean that the URI identifies the HTML. HTML is
> > one *representation* of the resource, not necessarily the resource
> > itself.
>
> Not everyone subscribes to this view. Most people would be very
> surprised if /mark-baker.jpg sent them an mp3 of a cricket match.
You claim that you like REST but not HTTP. REST is great and simple, but
HTTP is too complicated. But then you argue against the central tenets
of REST. Nothing Mark says above has anything to do with HTTP. It is all
REST.
"REST is defined by four interface constraints: identification of
resources; manipulation of resources through representations;*
self-descriptive messages; and, hypermedia as the engine of application
state."
"This abstract definition of a resource enables key features of the Web
architecture.
First, it provides generality by encompassing many sources of
information without
artificially distinguishing them by type or implementation. Second, it
allows late binding
of the reference to a representation, enabling content negotiation to
take place based on
characteristics of the request." But you don't like content negotiation
either...
If you don't like REST, that's okay. Propose another model.
Paul Prescod
|
