- From: Miles Sabin <miles@milessabin.com>
- Date: Mon, 6 Jan 2003 15:23:15 +0000
- To: www-ws-arch@w3.org
Mark Baker wrote,
> Miles Sabin wrote,
> > In the REST case we have to have,
<snip>
> > 2. A client application that can determine that a GET issued on
> > http://www.stockquotes.com/ibm/lastshareprice will make a
> > useful step forward in the interaction between it and the
> > server.
> >
> > In the RESTless case we have to have,
<snip/>
> > 2'. A client application that can determine that a POST issued with
> > getLastSharePriceOfIBM in the request entity will make a useful
> > step forward in the interaction between it and the server.
<snip/>
>
> (2) doesn't require that the client posess any additional a priori
> information than what's in RFCs 2616 and 2396 in order to get the
> data; (2') does.
Oh good grief!
Of course it does Mark. I requires that the client,
i) has the URI http://www.stockquotes.com/ibm/lastshareprice.
ii) knows that issuing a GET on that URI will do something useful in the
context of the current interaction.
Where in RFCs 2396 and 2616 does it say anything about that?
I'd like you to explain _in_detail_ why these two conditions are less
demanding than the corresponding conditions for (2').
Cheers,
Miles
Received on Monday, 6 January 2003 10:23:47 UTC