Re: [wsrp-wsia] [change request #204] Fields for cache key

[Rich Thompson <richt2@us.ibm.com>]

My memory says we decided to only require that markupParams be part of the 
cache key in v1 even though most Consumers will want to include other 
fields as well. Do we want to revisit what fields are required to be part 
of such keys?

Rich Thompson




Rich Thompson/Watson/IBM@IBMUS
03/04/2003 10:44 AM
 
        To:     wsrp-wsia@lists.oasis-open.org
        cc: 
        Subject:        [wsrp-wsia] [change request #204] Fields for cache 
key


Document: Spec
Section: 6.1.2.
Page/Line: 27/33
Requested by: Andre Kramer

The sessionID field should be used when computing a cache key. Also, if 
the consumer allows the other runtimeContext fields (excluding extensions) 

to vary in a session or for users then these should also be included in 
the cache key computation. Especially of note here is userAuthentication 
which may cause portlets to render security sensitive content. 

Reason: RuntimeContext can vary per portlet session as well as per user 
session. Same could be said for PortletContext.portletState and 
UserContext.


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