[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [wsrp-wsia] [I#124] concept of window ID (JSR168)
My understanding is that JSR168 exposes a windowID to portlets so they can namespace multiple instances of themselves within a shared session. WSRP exposes no such concept. This seems like a particular Producer to entity issue. Key question for me is whether means are provided for the Producer to supply the functionality. Obvious choices include: 1. Producer manages creating a unique id and encodes it in the refHandle for subsequent invocations. 2. For JSR168 Producers not using refHandles, use the fact that JSR168 Producers are going to set requiresCookieSupport to ’true’. In addition to the JSessionID cookie that will be shared by all portlets in a portlet application, use a portlet specific cookie to store this unique id (Producer still creates/manages the id). Gil Tayar <Gil.Tayar@webcol To: wsrp-wsia@lists.oasis-open.org lage.com> cc: Subject: [wsrp-wsia] [I#124] concept of window ID (JSR168) 10/30/2002 01:45 AM Status: Active Topic: Interface Class: Technical Raised by: Alejandro Abdelnur Date Added: 30-Oct-2002 Title: concept of window ID (JSR168) Description: JSR168 defines the concept of windowID. OPEN, waiting on WSRP. WSRP has to discuss the introduction of the consumer managed refHandle. ---------------------------------------------------------------- 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