W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2001

new use case DS24: caching

From: Nilo Mitra (EUS) <EUSNILM@am1.ericsson.se>
Date: Mon, 29 Jan 2001 13:24:44 -0600
Message-ID: <B1C9E91DC664D411A02D0050DA2AC6C01FEF0C@eamlynt753.ena-east.ericsson.se>
To: "'XP-PUBLIC'" <xml-dist-app@w3.org>
DS24: Caching
Some applications may wish to make caching possible for latency, bandwidth use or other gains in efficiency. To enable this, it should be possible to assign cacheability in a variety of circumstances. For example, "read" caching might be used to store messages at intermediaries for reuse in the response phase of the request/response message exchange pattern. Such caching might be on the scope of an entire message, an XP module, or scoped to individual XP module elements.
Similarly, "write" caching may be useful in situations when a request message in a request/response message exchange pattern (as well as similar messages in other message exchange patterns) does not need to be immediately forwarded or responded to. Such cachability might be scoped by different methods, as outlined above. 
Cacheability scoped by different elements might be associated by an attribute to the target element, through use of XML Query or XPath to describe the target elements in a header, or implied by the document schema, for example. 
Cacheability mechanisms applied to messages, bodies or elements might include time-to-live (delta time), expiry (absolute time), entity validation, temporal validation, subscription to invalidation services, and object update/purge. 
Finally, some applications may be capable of describing the dependencies and relationships between message elements. For example, a response element may be applicable to a wide range of requests; it would be beneficial to describe this element's relationship with request elements, so that it may satisfy a wide range of requests in an economical fashion. Similarly, the presence of a particular element may be a trigger for a cacheability mechanism to be applied to another element, such as validation or invalidation.
Copied from: http://lists.w3.org/Archives/Public/xml-dist-app/2001Jan/0109.html 

Nilo Mitra			phone:+1 212-295-8467
Ericsson			fax: +1 212-295-8489
100 Park Avenue		mobile: +1 917-913-4766
NY, NY 10017		email: nilo.mitra@ericsson.com
Received on Monday, 29 January 2001 14:27:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:11:30 UTC