[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - ex-9 - participant identification in context-reply
This issue has been added to the btpex issue list. The issues list is posted as a Technical Committee document to the OASIS BTP TC pages on a regular basis. The current edition, as a TC document, is the most recent document with the title in the "Issues" folder of the BTP TC document list - the next posting will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.
There are already several ways that this can be done with BTP, but they are all rather application-specific. At present, one could:
None of these could readily be supported by generic software in the way a propagated context could be in the opposite direction. There should be some general way.
Submitter's proposal: A possibility would be to allow an inferior identifier to be placed in the CONTEXT-REPLY, which would have similar semantics to having an CONTEXT-REPLY&ENROL&application message related group as far as association was concerned.
Alternatively, the presence of an inferior name qualifier on a CONTEXT-REPLY could be defined as having the similar meaning.
Note that both of these are essentially using CONTEXT-REPLY as just the standardised carrier of this information, rather than invent another message (REVERSE-CONTEXT ?) just for this purpose.
Changes: 23 Mar 2004 - new issue
To comment on this issue, please follow-up to this announcement on the business-transaction@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - ex-9 - [anything]" or is a reply to such a message.
To add a new issue, please email to the issues list maintainer (Peter Furniss).
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]