Re: [wsrp-interfaces] Fw: [wsrp] Additional use cases for issue #44(set new public params)

[Subbu Allamaraju <subbu@bea.com>]

> If the render URL is used and they are shared parameters wouldn't the 
> consumer have to be careful in calling portlets, since it may effect 
> other portlets interested in the parameter value. i.e. order and which 
> portlets i.e. to update cache
>   Rich -> It means that Consumers have to decode the URL before invoking 
> any portlets so that any shared PPs can be sent to all interested portlets.

Unlike the event model, in this case, Consumers decide who the 
interested parties are. From an implementation point of view, this could 
mean scoping choices like (a) scoped to the current portlet, (b) scoped 
to the current request, (c) scoped to the current user's session, (d) 
scoped to the current user forever, and (e) scoped to some/all users.

Due to security/privacy issues, Consumers may be forced go with (a) or 
(b), which is limiting the model, IMO.

Subbu