OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsrm] Action item 052504-4 - Clarification of HTTP Binding


Tom,

The current wording says that if a request is sent using HTTP transport 
protocol, then the requester cannot ask that the ack be sent using SMTP 
(or an other protocol).

IMHO, this is too restrictive. All we need to say is:

1) If the request is using SOAP 1.1 protocol then the ack/reply must use 
SOAP 1.1. Similarly if the request is using SOAP 1.2 protocol then the 
ack/reply must use SOAP 1.2
2) If the ReplyTo contains only a URL which uses the 'http:' URL scheme, 
then
a) the ack/reply must use the section 6 SOAP 1.1/HTTP binding, if using 
SOAP 1.1
b) the ack/reply must use the SOAP 1.2 HTTP binding for request/reply 
MEP, if using SOAP 1.2.

This is necessary because a URL does not indicate which binding to use 
and there are multiple binding that use HTTP as the transport protocol.

Suggested amendments are inlined below.

HTH.

-Anish
--

Tom Rutt wrote:

> Attached is the output of the action item to clarify the HTTP binding.
> 
> -----
> 
> 
> ----------------------------------------------------
> Tom Rutt    email: tom@coastin.com; trutt@us.fujitsu.com
> Tel: +1 732 801 5744          Fax: +1 732 774 5133
> 
> 
> 
> ------------------------------------------------------------------------
> 
> 1     Clarification of the Introduction of section 6, HTTP
> 
> Binding.
> 
> Replace the intro paragraph for section 6 (lines 1206
> 
> thru 1211) from:
> 
> “
> 
> This section describes the three binding pattern -
> 
> “Response”, “Callback”, and “Poll” binding pattern for
> 
> HTTP. These binding pattern is identified by the value of
> 
> ReplyPattern element (See Section4.2.3 for detail). This
> 
> specification expects that the transport layer will not
> 
> deliver a corrupted message to the reliability layer.
> 
> When a request message contains AckRequested element,
> 
> upon receipt of a reliable message, the Receiving RMP
> 
> MUST send a reply. This reply MUST be either an
> 
> Acknowledgment Indication or an RM Fault Indication. This
> 
> reply MUST be sent by specified binding pattern in the
> 
> ReplyPattern element of the request message.
> 
> “
> 
> to
> 
> “
> 
> This section specifies two normative bindings of WS-
> 
> Reliability header elements to SOAP header blocks carried
> 
> using HTTP as a transport protocol.
> 
> •     SOAP 1.1 over HTTP POST binding: An implementation
> 
> of WS-Reliability MAY support mapping the ws reliability
> 
> header elements as soap header blocks in accordance with
> 
> the SOAP 1.1 HTTP Binding, as specified in Section 6 of
> 
> SOAP 1.
> 
> •     SOAP 1.2 over HTTP POST: An implementation of WS-
> 
> Reliability MAY support mapping the ws reliability header
> 
> elements as soap header blocks in accordance with the
> 
> SOAP 1.2 HTTP binding for the request/response MEP, as
> 
> specified in Section 7, SOAP HTTP Binding, of SOAP 1.2
> 
> Part 2:
> 
> If a reliable message request is invoked using SOAP 1.1
> 
> over HTTP POST binding, all subsequent message exchanges
> 
> pertaining to that message ID MUST use the SOAP 1.1 over
> 
> HTTP POST binding.

Suggested amendment:

"If a reliable message request is invoked using SOAP 1.1, all subsequent 
message exchanges pertaining to that message ID MUST use the SOAP 1.1 
protocol."

> 
> A ReplyTo element present in a Request element or Poll
> 
> Request element sent using the SOAP 1.1 over HTTP POST
> 
> binding, MUST use the URI form of reference, with an
> 
> http: uri to use for invoking the ws reliability
> 
> response, in accordance with the SOAP 1.1 over POST
> 
> binding.
> 

Suggested amendment:

"If a ReplyTo element present in a Request element or Poll Request 
header element, sent using the SOAP 1.1 protocol, contains only a URL 
and uses the 'http:' URL scheme, then the WS reliability response MUST 
be sent using the HTTP binding specified in section 6 of SOAP 1.1.

> If a reliable message request is invoked using SOAP 1.2
> 
> over HTTP POST binding, all subsequent message exchanges
> 
> pertaining to that message ID must use the SOAP 1.2 over
> 
> HTTP POST binding.
> 

Suggested amendment:

"If a reliable message request is invoked using SOAP 1.2,
all subsequent message exchanges pertaining to that message ID MUST use 
the SOAP 1.2 protocol."

> A ReplyTo element present in a Request or Poll Request
> 
> header element sent using  the SOAP 1.2 over HTTP POST
> 
> binding, MUST use the URI form of reference, with an http
> 
> uri to use for invoking the ws reliability response, in
> 
> accordance with the SOAP 1.2 over POST binding.
> 

Suggested amendment:

"If a ReplyTo element present in a Request element or Poll Request 
header element, sent using the SOAP 1.2 protocol, contains only a URL 
and uses the 'http:' URL scheme, then the WS reliability response MUST 
be sent using the HTTP binding for request/response MEP specified in 
SOAP 1.2

> The following subsections specify the mapping of ws
> 
> reliability header elements to HTTP request and response
> 
> messages, for the three rm-reply patterns.  The Poll
> 
> reply pattern has two variations (synchronous and
> 
> asynchronous).  
> 
> The specific reply pattern in use is identified by the
> 
> value of ReplyPattern element (See Section4.2.3 for
> 
> detail). This specification expects that the transport
> 
> layer will not deliver a corrupted message to the
> 
> reliability layer. When a request message contains
> 
> AckRequested element, upon receipt of a reliable message,
> 
> the Receiving RMP MUST send a reply. This reply MUST be
> 
> either an Acknowledgment Indication or an RM Fault
> 
> Indication.  For the Callback and Poll reply patterns, a
> 
> ws reliability response element can contain multiple
> 
> acknowledgement and/or rm fault indications.
> 
> For simplicity, the detailed examples only show the use
> 
> of SOAP 1.1.  However, the figures showing the mapping of
> 
> ws reliability elements to HTTP POST request messages and
> 
> HTTP response messages apply to both the SOAP 1.1 over
> 
> HTTP POST binding, and the SOAP 1.2 over HTTP POST
> 
> binding.
> 
> 2     change Binding Pattern to reply pattern
> 
> Lines: 1212, 1223, 1253, 1274, 1289, 1328, 1348, 1354,
> 
> 1369, 1410, 1414, 1430,
> 
> 3     clarification that response goes on http post for
> 
> callbacks
> 
> the text for lines 1285 and 1286
> 
> “
> 
> (3) The Acknowledgment Indication is sent with another
> 
> HTTP connection from the Receiving RMP to the Sending
> 
> RMP. Example 14 is an example of this message.
> 
> “
> 
> does not require sending the rm: response on an HTTP Post
> 
> operation.
> 
> Also the text for lines 1425 thru 1427:
> 
> “
> 
> (5) The HTTP request corresponding to the Poll request in
> 
> (3) includes Acknowledgment Indication and/or Reliable
> 
> Messaging Fault. Example 18 is an example for this
> 
> message. This request is sent to the listener identified
> 
> the ReplyTo element in the PollRequest element.
> 
> “
> 
> does not require sending the rm: response on an HTTP Post
> 
> operation.
> 
> Clarify both of these sentences by stating that the HTTP
> 
> POST operation is used to send the  response.
> 
> 
> ------------------------------------------------------------------------
> 
> 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]