HTTP is not well understood [was: My top two issues]

[in hopes of being able to find these in the future...
please, (a) one issue per message, unless
they're technically related, and (b) put
some technical keywords in the subject]


On Mon, 2001-12-17 at 16:22, Mark Baker wrote:
[...]
> Issue; HTTP is not well understood
> 
> I assert that the entire Web Services phenomena exists because of a
> misunderstanding about what the HTTP protocol is about (and a whole
> lot of marketing $$$ 8-).  IMO, it is critical that the TAG document the
> generality of its application semantics.  While it is true that there
> are Web-friendly uses of SOAP (which I remain the most outspoken
> proponent of in the XML Protocol working group), I've yet to see an
> independant developer using it in this way.  The TAG could save a lot of
> people a lot of time and frustration by explaining the role and
> relevance of HTTP to the Web.
> 
> In response to a lot of Web Services propaganda that's been floating
> around the industry for the past while, I took at stab at doing this by
> writing up an Internet Draft called "An Abstract Model for HTTP Resource
> State"[2], which takes the view of HTTP as a state manipulation
> language.
> 

>  [2] http://www.markbaker.ca/2001/09/draft-baker-http-resource-state-model
> 
> MB

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/

Received on Monday, 17 December 2001 17:37:37 UTC