IMO, if you are doing a one-way asynch
message pattern over HTTP, with asynch
ack on a separate channel in the reverse
direction, then the HTTP response for the
original POST should be a 202 Accepted.
That response should be returned WITHOUT
any processing (MSH or application-level)
of the message, which is what 202 implies.
So, from the receiving end, it would
be:
1) receive message
2) send 202 response
3) dispatch message to MSH for processing
and eventual dispatch to application.
Cheers,
Christopher Ferris
Architect, Emerging e-business Industry Architecture
email:
phone: +1 508 234 3624
Mike Dillon - Drummond Group <>
wrote on 10/17/2002 11:18:00 AM:
> Hi all,
>
> In the current DrummondGroup ebXML Messaging Interop
> we have a issue that would be really helpful to have input
> from the committee. This is somewhat subtle but
> but thorny problem that we are having in the current
> DGI ebXML Messaging interop.
>
> The problem is on an asynchronous message with
> acknowledgment. Some implementations are returning
> the ack before the original http response...
> In other words, I post a message to you and I'm
> waiting for the http reply, I receive the ack
> first, then I receive the http reply. This obviously
> has a big effect on the architecture of an MSH solution.
>
> Do you'all have any comment on this ?
>
> Thanks !
>
> mike dillon
>
> 817 875 0794
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
