[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: RefToMessageID
<Martin> The only role the Messaging Spec needs to play is to provide an application-independent place to carry this piece of information in normal messages. Application independence is significant since this field is one which B2B middleware might process. </Martin> <Jacques> These practical considerations aside (I do not see any problem with providing to an app the MSH service of accessing and setting RefToMessageId), ... I am mostly motivated here in avoiding to the application the need to deal with IDs that are not business level, but again it does not hurt to have the MSH allow for this, as it can be useful in cases I may not have in mind. It becomes mostly an app design decision to use it or not (after all, V0.91 says that RefToMessageId MUST contain a valid ref value *when present*...) </Jacques> It is nice to see that we are thinking along these lines. Regards, Nikola
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC