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: [ebxml-msg] Comments on SyncReply


You said this statement is incorrect in section 7.5.5:

(1)     if syncReply is set to true and if the CPA indicates an application
response is included, ignore the received message (i.e. no message was generated
in response to the received message, or the processing of the earlier message is
not yet complete)

I agree, but I don't know how to change this.  I think the Receiver should go
ahead and bundle the 'HTTP 200 OK' together with any MSH signals (Acks, Errors,
Pongs, StatusResponse, DeliveryReceipt) and send these back immediately without
waiting for Business Responses.  The channel should then be left open waiting
for Business Signals/Replies.

IMO, SyncReply simply changes the role of each party concerning closing the
connection.  If SyncReply=false, then the sender is responsible for closing the
connection.  If SyncReply=true, then the Receiver is responsible for closing the
connection.  The receiver MUST be able to handle the case where SyncReply=true
but there is no Response to send back.  I have serious doubts about the utility
of holding connections for Business Responses since in many cases there will be
human intervention required.  There is perhaps a good use case for holding the
connection for Business Signals.  IMO, MSH signals should be sent with the '200

What shall we do?


David Fischer
Drummond Group.

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

Powered by eList eXpress LLC