RE: Why GET is an application semantic

> From: Mark Baker [mailto:distobj@acm.org]
[snip]
> Eventually however, generalization has to end.  I suggest that this
> is as far as one can go with it;
> 
> get( http://nasdaq.org/quotes/stock/realtime/sunw )
> 
> otherwise known as;
> 
> GET http://nasdaq.org/quotes/stock/realtime/sunw
> 

But why end there?  :-)
What about:

[GET] http://nasdaq.org/get?what=quotes&type=stock&symbol=sunw

I tend to read the HTTP GET as a protocol-intrinsic method upon 
which application semantics can be freely built (by app developers).
Am I "web-arch'ly incorrect" in this regard?

Joe Hui
Exodus, a Cable & Wireless service
=========================================

> I hope that helps explain at least this little piece of Web
> architecture.
> 
> MB
> -- 
> Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
> Ottawa, Ontario, CANADA.               distobj@acm.org
> http://www.markbaker.ca        http://www.idokorro.com
> 
> 

Received on Tuesday, 18 June 2002 22:51:41 UTC