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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

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


Subject: Re: [ebxml-msg] SynchReply module


Title: RE: [ebxml-msg] SynchReply module
Bob,

I believe that there are cases where is *is* necessary. The SHOULD refers
to the receiver's ability to keep open a connection indefinitely (which is
unlikely). In the event that the connection is broken, then the sender will
likely not ever receive a response.

This wording may need some further work;-)

Chris

Miller, Robert (GXS) wrote:
6EE295F4F386AC48B4FF6EB0CDBABD74B3A11C@ROC04BXGEISGE.is.ge.com">

Chris,

"There are use cases where it is necessary ..." ... "the
connection over which the message was received SHOULD be kept open"

So is it really necessary or not?  I like "SHOULD", and think the word 'necessary' is a bit too strong.  I'd vote for 'desirable' as a replacement word.

Cheers,
        Bob

-----Original Message-----
From: Christopher Ferris [ mailto:chris.ferris@sun.com ]
Sent: Thursday, November 15, 2001 8:10 AM
To: ebXML Msg
Subject: [ebxml-msg] SynchReply module


All,

Here is the proposal for the SyncReply module.

Cheers,

Chris

X SyncReply Module

There are use cases where it is necessary for the sender of a message, using
a synchronous communications protocol, such as HTTP, to receive the
associated response message over the same connection that the request
message was delivered. In the case of HTTP, the sender of the HTTP request
message containing an ebXML message needs to have the response ebXML
message delivered to it on the corresponding HTTP response message.

In the case where there are intermediary nodes (either ebXML MSH nodes or
possibly other SOAP nodes) involved in the message path, it is necessary
to provide
some means by which the sender of a message can indicate that it is
expecting a response
so that the intermediary nodes can keep the connection open.

The SyncReply ebXML SOAP extension element is provided for this purpose.

X.1 SyncReply element

The SyncReply element MAY be present as a direct child descendant of the
SOAP Header
element. It has the following attributes:
    - SOAP actor attribute with a value of
" http://schemas.xmlsoap.org/soap/actor/next "
    - SOAP mustUnderstand attribute with a value of '1' or 'true'

If present, this element indicates to the receiving SOAP or ebXML MSH
node that the
connection over which the message was received SHOULD be kept open in
expectation
that a response message will  be returned via that same connection.






----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: < http://lists.oasis-open.org/ob/adm.pl >




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


Powered by eList eXpress LLC