I have apparently been taken in by the REST koolaid, as for a long
time I would have completely agreed with Ralph.
However it seems to me that a URI is an _Identifier_ for a resource,
which is orthogonal to the representations that it can provide on
demand, and any other such 'run time' requirements. These belong in
the headers and can be very different between clients and between
requests, based on those changing requirements.
Rob
On Tue, Jun 1, 2010 at 1:06 PM, Ed Summers <[log in to unmask]> wrote:
> On Tue, Jun 1, 2010 at 2:21 PM, LeVan,Ralph <[log in to unmask]> wrote:
>> I've been sensing a flaw in HTTP for some time now. It seems like you
>> ought to be able to do everything through a URL that you can using a
>> complete interface to HTTP. Specifically, I'd love to be able to
>> specify values for HTTP headers in a URL.
>
> It might help (me) if you describe what you are trying to do first.
>
> //Ed
>
|
