RE: Questions prompted by the publication of WS-ReliableMessaging
"Anne Thomas Manes" <[email protected]> Mon, 17 Mar 2003 15:43:03 -0500
| Newsgroups | gmane.comp.web.services.ws-arch |
|---|---|
| Message-ID | <[email protected]> |
+1!!!! > -----Original Message----- > From: [email protected] [mailto:[email protected]]On > Behalf Of Ugo Corda > Sent: Monday, March 17, 2003 2:59 PM > To: [email protected] > Cc: [email protected] > Subject: RE: Questions prompted by the publication of > WS-ReliableMessaging > > > > How about working on the OASIS TC to augment the WS-Reliability > spec with the necessary additions (you already mention below that > a metadata mechanism is on the list of future OASIS TC > capabilities), instead of just going a completely separate way? > > Ugo > > > -----Original Message----- > > From: Jon Dart [mailto:[email protected]] > > Sent: Monday, March 17, 2003 11:46 AM > > To: Ugo Corda > > Cc: [email protected] > > Subject: Re: Questions prompted by the publication of > > WS-ReliableMessaging > > > > > > Ugo Corda wrote: > > > WS-Reliability does not seem to preclude supporting > > bindings other than HTTP. > > > > Indeed. But there are numerous practical obstacles to having > > it support > > MOM. I won't list them all, but one crucial difference is that > > WS-ReliableMessaging uses policy assertions to publish > > messaging options > > in the form of shared metadata. In the OASIS spec, there is > > no metadata > > (WSDL is a "futures" item), so everything is done in the SOAP > > headers. > > What if your messaging system needs to set up reliable > > delivery options > > before it can receive a message? Not possible in the present > > form of the > > spec. > > > > --Jon > > > > > > > > > > >