- From: Damodaran, Suresh <Suresh_Damodaran@stercomm.com>
- Date: Fri, 21 Jun 2002 19:06:40 -0500
- To: "'Mark Baker'" <distobj@acm.org>
- Cc: www-ws-arch@w3.org
-----Original Message----- From: Mark Baker [mailto:distobj@acm.org] Sent: Friday, June 21, 2002 12:28 PM <snip> FWIW, what I was getting at was that HTTP is special amoungst application protocols, because it is the only one that has any notion of a URI, and therefore any notion of discoverability in all contexts. FTP existed long before URIs, and before URIs became common place there was no way to identify a FTP resource; you had to write it down like "FTP site; garbo.uwasa.fi, /pub/software". So URIs are great, because they make previously universally undiscoverable resources, universally discoverable. And HTTP GET is just as great, because it can be used to resolve all of these things. So "restricting" yourself to GET isn't actually a restriction (though I'd agree that we could separate the semantic from the protocol, so that other Web architecture friendly application protocols, whenever anybody builds one, are supported). <snip> Yes, I agree. This truly is the middle ground:-) The key is separating the semantics from the protocol. Lets hope we do it right. Regards, -Suresh Sterling Commerce
Received on Friday, 21 June 2002 20:07:15 UTC