Re: [wsrp] Public parameters - caching

This would change the semantics significantly,
but could also provide quite a performance boost for large public parameter
sets. Effectively this would change the lifetime of the parameters from
a Portlet perspective to the session level ... currently they are defined
to be at the request level. There would be a variety of impacts of such
a change, but it definitely is an optimization to consider. Issues I see
include:

1. Would Consumers implement the bookkeeping
needed to track what  PP has changed since the last communication
with each portlet (would have to take into account cache hits)?

2. How would this impact stateless Portlets
(i.e. no session)?

3. Impacts on caching strategies where
an independent cache sits between the Consumer and Portlet?

Rich 

Subbu Allamaraju <>

05/31/05 02:53 PM

To

wsrp <>

cc

Subject

[wsrp] Public parameters
- caching

Since public parameters are supplied with each 

getMarkup/pbia/handleEvents request, isn't there a need to let Producers

to store these values in the session (just like URL templates and user

profile items), and let Consumers supply these values once per session?

This will be a nice performance optimization.

I did not find any references to this issue in the interfaces SC docs.

Has this issue been discussed previously?

Regards,

Subbu

---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that

generates this mail.  You may a link to this group and all your TCs
in OASIS

at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php