W3C home > Mailing lists > Public > xml-dist-app@w3.org > July 2001

Re: A tale of two bindings

From: Rich Salz <rsalz@zolera.com>
Date: Wed, 25 Jul 2001 09:48:49 -0400
Message-ID: <3B5ECE41.224116DD@zolera.com>
To: Eugene Kuznetsov <eugene@datapower.com>
CC: Jacek Kopecky <jacek@idoox.com>, mark.baker@sympatico.ca, xml-dist-app@w3.org
> I disagree -- unless there is a well-standardized Content-Type
> that is SOAP-specific (IOW, "app/soap+xml", not "text/xml"), the
> various intermediaries, security devices and so on will have a
> difficult time figuring out if "/site/foo/bar.cgi" is SOAP or
> a web page request.

So what?  If intermediaries are going to do content-based filtering,
then they'll need to know the syntax and semantics.  As for your example
above, on my host /site/foo/bar.cgi is a static web page.

> What you are saying makes perfect sense when it goes from end-to-
> end, but the picture gets more difficult as one starts adding
> various SOAP and non-SOAP intermediaries along the way.

I disagree.  It makes the "tunnel" viewpoint more compelling.

	/r$
-- 
Zolera Systems, Securing web services (XML, SOAP, Signatures,
Encryption)
http://www.zolera.com
Received on Wednesday, 25 July 2001 09:48:22 GMT

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