RE: [wsrp-wsia] [change request #209] Invalidates "cached" markup

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

That portion of this statement hasn't changed. I do think that is at least 
a logical result of our definition of perUser caching scope.

Rich Thompson




"Kropp, Alan" <Alan.Kropp@vignette.com>
03/06/2003 01:40 PM
 
        To:     Rich Thompson/Watson/IBM@IBMUS, 
wsrp-wsia@lists.oasis-open.org
        cc: 
        Subject:        RE: [wsrp-wsia] [change request #209] Invalidates 
"cached" markup


This statement implies that UserContext is a required part of the cache 
key
for perUser scoped caches.  Is this our intent?

-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Wednesday, March 05, 2003 7:53 AM
To: wsrp-wsia@lists.oasis-open.org; Rich Thompson
Subject: [wsrp-wsia] [change request #209] Invalidates "cached" markup






Document: Spec
Section: 6.1.4
Page/Line: 27/24
Requested by: Rich Thompson

Old text: ”perUser”: The markup is specific to the userContext for which 
it
was generated. Changes to the data of the UserContext MUST invalidate the
markup.

New text: ”perUser”: The markup is specific to the userContext for which 
it
was generated. Changes to the data of the UserContext MUST invalidate the
cached markup.

Reasoning: Clearer language.

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



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