RE: [wsrp-wsia] Creating an issue - RuntimeContext

[Andre Kramer <andre.kramer@eu.citrix.com>]

On important case (for JSR 168) is when initCookie() has been used to
establish an http session. The http session cookie can be used to scope
entityInstanceKeys just like a registration could.

In this case, it seems wrong to duplicates consumer logic to handle both
types of session (http and WSRP). I have an issue in the pipeline to discus
making our SessionContext/SessionID effective only when no http session is
explicitly set up by the consumer.

regards,
Andre

-----Original Message-----
From: Subbu Allamaraju [mailto:subbu@bea.com]
Sent: 17 December 2002 17:41
To: wsrp-wsia@lists.oasis-open.org
Subject: Re: [wsrp-wsia] Creating an issue - RuntimeContext


Rich Thompson wrote:
> 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.

Even when the consumer supplied an entityInstanceKey, I'm unclear of how 
the producer can use it to uniquely associate data with an entity. What 
happens if two consumers supply the same entityInstanceKey (say, for 
producers not supporting registration)?

> 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.

If I'm not mistaken, the same question applies here as well.

Regards,

Subbu


> 
> 
> 
> 
> 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>
> 
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>