W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2005

Jabber Binding Supports Request/Response - existence proof of shared MEPs

From: <noah_mendelsohn@us.ibm.com>
Date: Thu, 22 Dec 2005 14:46:51 -0500
To: xml-dist-app@w3.org
Message-ID: <OFCCB8629D.127CD4A9-ON852570DF.006BB332-852570DF.006CA978@lotus.com>

In recent discussions, some people have asserted that one measure of 
benefit of having MEPs in SOAP is whether we've seen more than one binding 
that supports the same MEP.  I just checked and the draft Jabber binding 
does, as I thought, support 
http://www.w3.org/2003/05/soap/mep/request-response/, the same 
Request/Response pattern that's supported by our standard HTTP binding. 
See [1].  Presumably, users will get the benefit of having a high degree 
of similarity in the interfaces needed to support HTTP and Jabber. 
Interestingly, this also suggests that we'll have to coordinate with the 
Jabber folks if we make the response envelope optional, drop the 
Request/Response MEP entirely, etc. as their draft specification clearly 
depends on our MEP in its current form. 

Anyway, Jabber's use of our MEP reinforces my feelings that (a) MEPs as we 
have them in SOAP are a good thing and practical to reuse and (b) that 
others have dependencies on these aspects of our Recommendation and we 
should proceed with great caution in making any changes.

Noah

[1] http://www.jabber.org/jeps/jep-0072.html#binding-patterns

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------
Received on Thursday, 22 December 2005 19:47:07 GMT

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