Re: [wsrp] [Resource caching] wsrp-resourceCacheability = portlet

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

The portlet has complete say on whether
or not it  will require such Consumer processing! The sentence
following it goes on to explain it in a more concrete fashion; "This
restriction ... prohibits the use of URIs with a wsrp-urlType of render
or blockingAction."

Rich

Subbu Allamaraju <subbu@bea.com>

03/16/2007 01:39 PM

To	Rich Thompson/Watson/IBM@IBMUS
cc	wsrp <wsrp@lists.oasis-open.org>
Subject	Re: [wsrp] [Resource caching] wsrp-resourceCacheability = portlet

Isn't it the case the portlet has no say on "but
will not require 
Consumer processing which needs the state of any other portlet"?

I don't have a concrete suggestion, though.

Subbu

Rich Thompson wrote:
> 
> Good point. The intent may be better captured by:
> 
> "Resource URIs specifying a value of "portlet" are
telling the Consumer 
> that the resource needs access to the portlet state (e.g. 
> NavigationalContext), but will not require Consumer processing which
> needs the state of any other portlet."
> 
> Rich
> 
> 
> *Subbu Allamaraju <subbu@bea.com>*
> 
> 03/16/2007 10:42 AM
> 
>                  
> To
>                  wsrp
<wsrp@lists.oasis-open.org>
> cc
>                  
> Subject
>                  [wsrp]
[Resource caching] wsrp-resourceCacheability = portlet
> 
> 
>                  
> 
> 
> 
> 
> 
> The first sentence for the value "portlet" reads as
> 
> "Resource URIs specifying a value of "portlet" are
telling the Consumer
> that the resource needs access to the portlet state (e.g.
> NavigationalContext), but not the state of any other portlet. "
> 
> The part about "but not the state of any other portlet"
seems confusing.
>   No WSRP-compliant portlets can depend on the state of other
portlets
> while responding to gm/pbia/gr/he. Even if they want to get other
> portlets' state, they can get it :)
> 
> Subbu
> _______________________________________________________________________
> 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.
> 
_______________________________________________________________________
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.