W3C home > Mailing lists > Public > www-ws@w3.org > April 2003

RE: Protocol independence

From: Mark Baker <mbaker@idokorro.com>
Date: Wed, 9 Apr 2003 12:03:29 -0400
Message-ID: <0503561D34C63045B07F04E5B3B2BFDC152381@FRED.planetfred.internal>
To: "Geoff Arnold" <Geoff.Arnold@Sun.COM>
Cc: <www-ws@w3.org>

> So exactly how does CapeClear implement this architecture?
> 
> http://www.capeclear.com/images/tempimages/diagram.gif
> 
> If such configurations become common, no sane programmer or network 
> architect
> will ever rely upon varying message semantics based on 
> protocol or HTTP
> method. Even if the SOAP 1.2 spec does not preclude it, best practice
> will deprecate it......

Hey, if we're talking about what Web services folks are actually
*doing* then there's not much to discuss; yes, they're assuming
protocol independence in droves, including CapeClear in that
diagram. 8-)

I'm just here saying that there's a significant cost - in terms of
the loss of valuable properties exhibited by the various
architectural styles in use on the Internet today - in treating
app protocols as transport protocols.  The WSA arch doc has to
address this, IMO, if it is to be of use in helping developers
choose which architectural style to use.

MB
Received on Wednesday, 9 April 2003 12:03:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:41 GMT