[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [wsrp-wsia] Creating an issue - RuntimeContext
This text in the draft has been modified based on recent decisions to: entityInstanceKey: A unique, opaque string the Consumer MAY supply as a reference to this use of the entity. This reference MAY be used by the entity to properly separate data for multiple instances of the entity within any Producer-defined data sharing mechanisms. Since this reference may be used as such a key, its length MUST be less than 256 bytes and Consumers SHOULD keep it as short as possible. There has also been a suggestion to add a note that a Producer could use this as a reference in place of generating a sessionID and that such a use will likely have a positive impact on the Consumer's performance. Rich Thompson Subbu Allamaraju <subbu@bea.com> 12/17/2002 10:06 AM To: wsrp-wsia@lists.oasis-open.org cc: Subject: [wsrp-wsia] Creating an issue - RuntimeContext Topic: RuntimeContext Class: Minor Technical Title: Intent and scope of uniqueness of the entityInstanceID in the RuntimeContext Document Section: 5.1.2 Description: What is the intent of entityInstanceID in RuntimeContext? The spec is unclear about the difference between the producer-generated entityHandle and consumer-generated entityInstanceID. It appears that the producer will have to use both entityHandle and entityInstanceID to uniquely associate data with an entity. However, for producers not offering registration, the consumer generated entityInstanceID (along with entityHandle) is not adequate for guaranteeing uniqueness on the producer end. Regards, Subbu ---------------------------------------------------------------- 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