[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sca-bindings-comment] Response to: "Microsoft technicalcomment: Develop interoperable approach notspecific to SCA for callbacks"
Thank you for considering Microsoft's suggestion for improving the SCA Web Services Binding spec's interoperability (http://www.osoa.org/jira/browse/BINDINGS-87). We suggested that Web Services callbacks in the SCA Web Services Binging spec should interoperate with comparable frameworks such as JAX-WS and WCF, and not be limited to various implementations of SCA. This would promote the original goals of the Web Services standards to achieve wire-level interoperability among diverse run-times and platforms. The SCA Binding TC responded by saying that the SCA Web Services binding protocol "defines an *SCA* Web service callback protocol standard” and that it "is not meant to satisfy general purpose callback requirements with a broadest scope possible". In other works, the TC believes that the SCA Web Services callbacks will NOT be interoperable with non-SCA implementations The TC's response goes on to say that "This TC does believe that it should define an interoperable Web services protocol that implements SCA callback and it has done that. It does not believe that it is in the scope or interest of this TC to define a callback protocol for all architectures and programming models." We respectfully find this statement contradictory, unless the TC defines the term "interoperability" in its narrowest form: SCA implementations will only be interoperable amongst themselves, and not with other frameworks and runtimes. We would find this unfortunate, as OASIS is committed to broad interoperability, especially when it comes to use of Web Service wire protocols. It would be better to standardize a Web Services callback in a separate spec, with the participation of all vendors who build platforms and products that support Web Services wire protocols. It is clear from [1] that the TC is aware that interoperability with non-SCA runtimes is an issue. The TC discussed the idea of moving the callback portion of the protocol into its own document in order to address "the use case of non-SCA clients does walk into the more general territory alluded to by MS." We highly recommend that the Binding and Assembly TCs work together to design a Web Services Binding spec that is interoperable with non-SCA technologies. Without interoperability, software developers and users will find it difficult to use SCA in the heterogeneous, multi-vendor environments that all our customers live in. [1] http://www.oasis-open.org/committees/download.php/34064/SCA%20Bindings%20minutes%202009-09-03.doc Regards, Michael Champion From: Simon Holdsworth [mailto:simon_holdsworth@uk.ibm.com]
Unless stated otherwise above: |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]