W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2002

RE: FW: draft findings on Unsafe Methods (whenToUseGet-7)

From: Don Box <dbox@microsoft.com>
Date: Thu, 18 Apr 2002 18:28:44 -0700
Message-ID: <CFC4F26947496E4092489B2425614958045CF293@svc-msg-02.northamerica.corp.microsoft.com>
To: "Hutchison, Nigel" <Nigel.Hutchison@softwareag.com>, <jones@research.att.com>, <moore@cs.utk.edu>, <www-tag@w3.org>
Cc: <dorchard@bea.com>, <www-ws-arch@w3.org>, <xml-dist-app@w3.org>
> -----Original Message-----
> From: Hutchison, Nigel [mailto:Nigel.Hutchison@softwareag.com]
> Sent: Tuesday, April 16, 2002 9:44 AM
> To: 'jones@research.att.com'; moore@cs.utk.edu; www-tag@w3.org
> Cc: dorchard@bea.com; www-ws-arch@w3.org; xml-dist-app@w3.org
> Subject: RE: FW: draft findings on Unsafe Methods (whenToUseGet-7)
> 
> I personally find the prospect of having to buy a SOAP Cache from
(name
> your
> Web Services technology supplier) to make a web service scaleable,
instead
> of using existing web intermediary technology like Squid, somewhat
> distressing. Particularly if it could have been avoided by some
concerted
> activity in the W3C.

I'm sorry, but if I must chose between expressing most of my app in
terms of HTTP GET vs. having the switch/router/gateway/cache fabric get
smarter, I'll take the latter any day. 

I think SOAP-focused network infrastructure is inevitable and frankly a
good thing. 

As I recall, network infrastructure adapted to a new protocol (HTTP) in
the 1990's without the death or dismemberment of the Internet. 

It is happening again in this decade, since like it or not, SOAP seems
to be where networked applications are headed. 

DB
Received on Thursday, 18 April 2002 21:28:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:09 GMT