I've been working from option 3.
There are 2 key elements in the data model:
IPortalCookie, which represents a single Cookie Eric is referring to
(1 key to relate to all portlet cookies).
IPortletCookie, which mimics javax.servlet.http.Cookie per the portlet
spec, but also provides a reference to
That would actually be option 1. If we did option 3 the reference from
the IPortletCookie to IPortletEntity would go away and all portlets
would see all cookies for a particular browser.
-Eric
On 1/18/11 8:30 AM, Nicholas Blair wrote:
I've been working from option 3.
There are 2 key elements
Oops! That makes sense though. Dropping the reference to
IPortletEntity within IPortletCookie would clear up some of the
troubles I ran into recently.
On Tue, Jan 18, 2011 at 9:01 AM, Eric Dalquist
eric.dalqu...@doit.wisc.edu wrote:
That would actually be option 1. If we did option 3 the
Hrm, that is a good point. The spec does refer to them in the same areas
where it refers to using portlet request/response properties as HTTP
headers which also implies no scoping. 3 would also be the easiest to
implement since then the cookies have no relation to the portlet
definition or
