RE: [wsrp-wsia] [change request #128] cache invalidation due to perform*Interaction()

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

I'm not sure this statement is conservative enough, as I believe all markup
for the portlet should be treated as expired after an action. MarkupParams
includes the navigational state and just invalidating markup cached under:
the current nav stat; the URL's nav state; the returned nav state, may not
be enough. Unless the portlet returns an updated cache control entry which
explicitly updates one (possibly) cached markup, all the portlet's markup
should be considered expired/invalid. This can be achieved by a consumer
maintaining a per-porlet content expiration time which is updated on
performXXXInteraction and using this to filter non-expired markup from the
cache(s).

regards,
Andre

-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: 06 February 2003 19:31
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [change request #128] cache invalidation due to
perform*Interaction()


Document: Spec
Section: 6.2.1.2
Page/Line: 39/10
Requested by: Rich Thompson
Old text: [insert new paragraph]
Proposed text: Consumers invoking either performInteraction() or 
performBlockingInteraction() MUST treat any markup cached for the 
equivalent MarkupParams (i.e. the MarkupParms structure passed to the 
invocation updated with any honored newMode or newWindowState requests and 
any returned navigationalState) as if the expiry time had elapsed unless 
the response includes a new CacheControl structure indicating the cached 
markup is still valid.

Reasoning: I had promised last Wednesday to post a proposal for how 
interaction processing impacts cached markup.

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