Re: [wsrp-interfaces] Groups - CacheableResources.html uploaded

[Subbu Allamaraju <subbu@bea.com>]

My interpretation is that, when a portlet is not relying on the portlet 
state, it means that the result would be equivalent to one served by the 
HTTP proxy.

You are right that this needs to defined explicitly.

I have a question on the second option (i.e. "portlet"). With resources, 
the consumer will most likely have no control on how the resource is 
being consumed at the user-agent. Since changes to the portlet's state 
can happen outside the request that generated the request, I don't see 
how the resource will be cacheable.

Subbu

Stefan Hepper wrote:
> Thanks Rich,
> looks good to me, the only thing I could not find was a definition in 
> the spec on portlet state.
> I assume you mean portlet mode, window state, navigational context, right?
> 
> Can we explicitly define this somewhere in the spec?
> 
> Stefan
> 
> richt2@us.ibm.com wrote:
>> The document named CacheableResources.html has been submitted by Rich
>> Thompson to the WSRP Interfaces SC document repository.
>>
>> Document Description:
>>
>>
>> View Document Details:
>> http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/document.php?document_id=22696 
>>
>>
>> Download Document:  
>> http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/download.php/22696/CacheableResources.html 
>>
>>
>>
>> PLEASE NOTE:  If the above links do not work for you, your email 
>> application
>> may be breaking the link into two pieces.  You may be able to copy and 
>> paste
>> the entire link address into the address field of your web browser.
>>
>> -OASIS Open Administration
>>
>>
>>
> 
> 
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.