OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsrp-interfaces] Issue with current CachableResource proposal


I am for adding it -- also copying the wsrp list in case anyone isn't on this one.
    -Mike-

Rich Thompson wrote:

I think it is a good idea to enable those Producers who can and are willing to enforce the restrictions.

Any objections to adding this field prior to the inclusion of the proposal into the draft?

Rich



Stefan Hepper <sthepper@hursley.ibm.com>

03/14/2007 12:02 PM

To
WSRP Interfaces subgroup <wsrp-interfaces@lists.oasis-open.org>
cc

Subject
[wsrp-interfaces] Issue with current CachableResource proposal







While discussing in the JSR 286 EG how the producer may enforce the
restrictions mentioned for the type FULL and PORTLET we noticed that the
producer does not get any information back on a serve resource call
about the cachability setting.
Therefore I propose to add the following on the ResourceParams type:
[O] string resourceCachability

providing the resourceCachability value set on the resource URL that
triggered this getResource call. If this value is missing the default is
that the cachability of the getResource call is of type PAGE.

Stefan





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]