[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: T2 Message ID in Response
Every message sent, whether at the behest of an external source (application) or in response to a received message (ack, dr, response) has its own unique MessageId. Cheers, Chris Colleen Evans wrote: > > A very basic question, but in looking through the 1.0 spec, > email threads, and issues log, I can't find an answer. > > MessageID uniquely identifies a message > RefToMessageID references that unique MessageID to identify > a message that an ack, status request / response, etc. > relates to. > > My assumption is that the sending MSH generates the unique > MessageID (based on the critera of RFC 2392). Does the > receiving MSH use the same MessageID for the response, or > does it generate a new, unique MessageID for the response > message and use the RefToMesageID to indicate that it is a > response to the sending MSH Message? > > I think the spec requires some text somewhere to clarify, or > it could be interpreted a couple of ways. > > Colleen > > -- > Colleen Evans > Principal Product Manager > Sonic Software Corporation > phone: 720 480-3919 or 303 791-3090 > email: cevans@sonicsoftware.com > http://www.sonicsoftware.com > > ---------------------------------------------------------------- > 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