OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [wsrp-wsia] [change request #155]



Is this giving the impression that the portlet is supposed to maintain a
"cache" of UserContext (profile too?) data, that gets updated during the
session by the Consumer?  It sounds useful, but it also sounds like
something we don't want to consider for 1.0.  The "full" user context gets
conveyed to the portlet upon initial render, right?  So worst case, the
changed profile data doesn't get reflected until the next time the user
initiates a session with this portlet.

What about stateless portlets?  How would they be expected to handle partial
UserContext?

Alan


-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Wednesday, February 19, 2003 8:03 AM
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [change request #155]


Document: Spec
Section: 5.1.11
Page/Line: 20 / 29
Requested by: Richard Jacob
Old text: Note that the Consumer MAY send UserContext information on any 
invocations regardless of the value of this flag.
Proposed text: Note that the Consumer MAY send UserContext information on 
any invocations as an update of any information the Portlet MAY be storing 
in a session.
Reasoning: Clearer semantics for when there is data in the session AND in 
the invocation. Same change for templatesStoredInSession.

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