When to use HTTP

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

Thanks.

MB
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Web architecture consulting, technical reports, evaluation & analysis

Received on Tuesday, 28 January 2003 10:28:17 UTC