W3C home > Mailing lists > Public > www-tag@w3.org > January 2003

Re: When to use HTTP

From: Dan Connolly <connolly@w3.org>
Date: Tue, 28 Jan 2003 17:35:27 -0600
To: Mark Baker <distobj@acm.org>
Cc: www-tag@w3.org
Message-id: <1043796926.29626.203.camel@dirk.dm93.org>

On Tue, 2003-01-28 at 09:29, Mark Baker wrote:
> Greetings,
> 
> >From the Jan 27 TAG teleconf minutes;
> >            DC: I suggest describing GET/PUT/POST in a para each, then say
> >            "if your app looks like that, use HTTP".
> 
> If I could make a friendly suggestion ...
> 
> That position - that if you've got hypertext, you use should use HTTP -

Er... that's not the position I was describing; it's quite the
opposite, in fact.

GET/PUT/POST works on lots of stuff besides hypertext.

> while entirely accurate, in my experience, doesn't provide very much
> guidance to those trying to decide what architecture to use.
> 
> For example, many Web services proponents frequently (and accurately!!),
> claim that they don't have any hypertext, and so therefore don't need to
> "use HTTP" (i.e. use things like URIs and GET).
> 
> So I suggest that a position such as "if your app can *reasonably* be
> made to look like that, use HTTP", would be superior from that
> perspective.

Yup.

> Thanks.
> 
> MB
-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Tuesday, 28 January 2003 18:35:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:15 GMT