[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrm] Input for FAQ question
A way to approach the composability with other WS-* specs is that they
are likely to fall under these (fuzzy) categories :
(a)- "Under WS-R": Add-ons to SOAP transport like routing, addressing,
that WS-R may need to accommodate or profile.
Status: nothing in the open space yet...
(b)- "Supporting WS-R" specifications (policies, WSDL annotation), that support some function
assumed by WS-R but not central to its deployment:
Status: not finalized or not open.
(c)- "Complementary to WS-R" specifications (Security, transactions, Context...)
that support other business requirements requirements likely to be used in conjunction with reliability, and share message footprint.
Soap headers composability and processing model make this possible. Apparent redundancy (message ID, reply address..) should not be an issue.
Appropriate profiling and guidelines may apply.
(d)- "Over WS-R", Higher level specifications (BPEL, Choreography, CAF, ASAP...)
would use/profile reliability, not the reverse.
That may help a bit I hope. Our focus would be on (c) this time.
Jacques
-----Original Message-----
From: Tom Rutt [mailto:tom@coastin.com]
Sent: Tuesday, April 06, 2004 9:39 AM
To: Tom Rutt
Cc: wsrm
Subject: Re: [wsrm] Input for FAQ question
Tom Rutt wrote:
> How can ws reliability be used with other ws reliability protocols.
This is a mistake it should read "How can ws-reliability be used with
other web service protocols.? "
> Answer :
> An important consideration in design of the WS-Reliability protocol
> was to have it be orthogonal to any other web services protocols which
> define the use of soap header elements.
>
> WS-Reliability defines elements to be sent in Soap headers . Our
> header elements only contain parameters essential for the operation
> of the WS-reliability protocol. For example, WS-reliability defines
> a reply to element for the sending Reliable Message Processor to
> convey a call back address for the Reliable messaging reply. This
> address is independent of any other reply mechanisms used for other
> protocols (e.g., WSDL response is not influenced by the WS-Reliability
> reply To parameter).
>
>
>
>
> .
>
>
>
--
----------------------------------------------------
Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744 Fax: +1 732 774 5133
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]