One could use HTTP in an asynchronous way. A sends B a request using HTTP;
the response is simply 200OK. B eventually sends a response by opening a
new HTTP connection to A and sending the response and receiving 200OK.
That's asynchronous at the ebXML level although HTTP is used for both the
request and response.
Regards,
Marty
*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
David Fischer <david@drummondgroup.com> on 11/20/2001 01:48:28 PM
To: David Fischer <david@drummondgroup.com>, Christopher Ferris
<chris.ferris@sun.com>
cc: Arvola Chan <arvola@tibco.com>, ebxml-msg@lists.oasis-open.org
Subject: RE: [ebxml-msg] Re: SyncReply Module
It appears that the answer to my first question is, this is a new use
case/new feature for a previously unmentioned/ unsupported set of
functionality.
OK, now my second question, why would syncReply ever be *false* for a
synchronous transport (for all scenarios pertinent to v1.0).� For all
asynchronous transports, syncReply is ignored, so its value is irrelevant
(see section 7.4.7).
- David.