Re: [wsrp-wsia] [I#190] Intent and scope of uniqueness of theentityInstanceID in the RuntimeContext

[Subbu Allamaraju <subbu@bea.com>]

Rich,

Could we have a more formal definition of "producer-defined data sharing 
mechanism"? From your description below, this mechanism seems to be 
referring to some run-time data sharing. If so, how does it relate to 
Sec 3.8 (Producer Mediated Sharing)?

Regards,

Subbu

Rich Thompson wrote:
> The intent of entityInstanceKey is Consumer assistance in disambiguating 
> between multiple uses of an entity on a "page". Producer implementations 
> can certainly make choices such that this is not useful for such 
> assistance, but it will be helpful for many implementations. My take from 
> the discussion to-date (and what I think the language says) is that this 
> key (when supplied) is unique for this Consumer.
> 
> Current language:
> 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.
> 
> 
> Rich Thompson
> 
> 
> 
> 
> Gil Tayar <Gil.Tayar@webcollage.com>
> 12/18/2002 04:03 AM
>  
>         To:     wsrp-wsia@lists.oasis-open.org
>         cc: 
>         Subject:        [wsrp-wsia] [I#190] Intent and scope of uniqueness 
> of the entityInstanceID in      the RuntimeContext
> 
> 
> Issue: 190
> Status: Active
> Topic: interface
> Class: Minor_Technical
> Raised by: Subbu Allamaraju
> Title: Intent and scope of uniqueness of the entityInstanceID in the 
> RuntimeContext
> Date Added: 18-Dec-2002
> Document Section:   v0.85/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, or producers not offering registration, the 
> consumer generated entityInstanceID (along with entityHandle) is not 
> adequate for guaranteeing uniqueness on the producer end.
> Resolution: 
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>