Re: How is this supposed to work?

[Christopher Ferris <chris.ferris@east.sun.com>]

All,

As Mark and Nikola have pointed out, the two
fields in the header (ConversationId and RefToMessageId)
can be used to match up a response to a query, as well 
as the TPA itself in many regards.

Cheers,

Chris
Mark Hale wrote:
> 
> I guess we're all up late.  Use Conversation Id in TPAInfo.
> 
>         Thanks,
> 
>         Mark
> 
> > -----Original Message-----
> > From: Yoshi Russell [mailto:yoshi.russell@xmls.com]
> > Sent: Monday, October 30, 2000 7:03 PM
> > To: Ebxml-Poc (E-mail)
> > Subject: How is this supposed to work?
> >
> >
> > FROM: JP Morgenthal using Yoshi Russell's e-mail:
> >
> > Please excuse this if it is a stupid question, but I'm a bit puncy from
> > coding for the last three days straight.
> >
> > It seems to me that this track 1 is being implemented with an asynchronous
> > protocol.  This means that the registry receives the
> > GetRootClassificationNodesRequest and responds to a URI that
> > corresponds to
> > the DUNS number in the request header asynchronously instead of
> > just sending
> > a response document back to a waiting client.
> >
> > Is this right? If so, how is the client supposed to match the messages up?
> > That is on the what part of the header must remain in tact in order for
> > matching to occur?
> >
> > If this is completely off base, please reset me.
> >
> > Thanks.
> >
> > JP