W3C home > Mailing lists > Public > www-ws-arch@w3.org > June 2002

RE: Why GET is an application semantic

From: Joseph Hui <Joseph.Hui@exodus.net>
Date: Tue, 18 Jun 2002 19:52:28 -0700
Message-ID: <45258A4365C6B24A9832BFE224837D551D1C4F@SJDCEX01.int.exodus.net>
To: "Mark Baker" <distobj@acm.org>, <www-ws-arch@w3.org>

> 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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:00 GMT