W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2003

Re: SOAP feature 51 implementation

From: Jacek Kopecky <jacek@systinet.com>
Date: 05 Feb 2003 13:59:58 +0100
To: David Fallside <fallside@us.ibm.com>
Cc: XMLP Dist App <xml-dist-app@w3.org>
Message-Id: <1044449997.12372.14.camel@krava.in.idoox.com>

David,

Systinet WASP Server for Java does support multiple transport bindings.
Implementing this is fairly easy due to decoupling SOAP message
framework from protocol bindings; with the caveat that apart from HTTP,
such bindings are not standardized and usually not interoperable.

Currently, WASP Server for Java includes the following transport
bindings: HTTP/HTTPS, email, JMS.

                   Jacek Kopecky

                   Senior Architect, Systinet Corporation
                   http://www.systinet.com/




On Fri, 2003-01-31 at 04:34, David Fallside wrote:
> 
> 
> 
> Implementers, we agreed a while ago that we would not test interop for
> feature 51 "support multiple transport bindings"
> (http://www.w3.org/2000/xp/Group/2/03/soap1.2implementation.html#f51).
> However, we also decided that we would collect statements from implementers
> to document the ease of implementing this feature. So, I am asking
> implementers to send brief emails to dist-app describing how easy or hard
> it was to implement this feature. I suggest each email (i) states whether
> the feature was relatively easy, average, or relatively hard to implement,
> and (ii) provide any additional comments about the ease of implementation.
> I'll link to these email statements from col 12, aka "Interop Traces".
> Please can you send in your statements towards the end of next week, say by
> CoB on thursday, Feb 6.
> Thanks in advance.
> 
> ............................................
> David C. Fallside, IBM
> Ext Ph: 530.477.7169
> Int  Ph: 544.9665
> fallside@us.ibm.com
Received on Wednesday, 5 February 2003 08:00:14 GMT

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