Re: [wsrp] [CR306] - Add default cacheControl

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

While this concept makes sense at the
platform level (i.e. the portlet developer doesn't always have to indicate
the cachability of markup as the platform will provide a default), I disagree
that this should get pushed out past the portlet container. I would rather
we follow the web model where the source of something is required to indicated
its cachability.

Rich

Rich Thompson/Watson/IBM@IBMUS

10/19/2004 08:59 AM

To	wsrp@lists.oasis-open.org
cc
Subject	[wsrp] [CR306] - Add default cacheControl

Document: Spec
Section: 5.1.11
Requested by: Subbu Allamaraju

Old Text:
New Text:   [O] CacheControl    cacheControl

Reasoning: We currently allow Producers to return cacheControl along with
markup so that the Consumer can try to cache the markup. However, the Consumer
will not know a priori whether a portlet's markup can be cached or not.
Some portlet programming models such as JSR168 allow portlet developers
to specify a default cache interval with the portlet's metadata. In the
current protocol, there is no means for exposing this metadata to Consumers
at discovery time in an interoperable manner.

By adding this field to the PortletDescription we can align WSRP with JSR168
more tightly.

Errata? no