V2 deferred use cases Twelveth face to face meeting October 4 th – 7 th, 2005 Dublin

October 4, 2005WSRP Technical Committee2 Portlet initiated cache invalidation There are times (e.g. due to external events, Producer-mediated coordination, etc) when a portlet can determine that previously cached content is now invalid

October 4, 2005WSRP Technical Committee3 Consumer managed portlet hierarchies WSRP declares there is no relationship between a POP and its clones Many systems actually support hierarchical relationships If Consumer knew the Producer supports hierarchical portlet relationships, management advantages could be realized

October 4, 2005WSRP Technical Committee4 Enhanced cooperation in producing markup Retailer including a manufacturer portlet with retailer’s prices/availability Reuse of Consumer-defined markup (e.g. buttons, form controls, etc) Ability for a portlet to reference an external system (provided by the Consumer, producer or completely external) without leaving the context of the Consumer Exposing controls over optional markup generation to the Consumer

October 4, 2005WSRP Technical Committee5 Leveraging other standards We have followed various grid and security standards for the past four years, several of which either are now (WS-I, WSS, SAML, etc) or shortly to become (WSRF, WSN, WS-I BSP, etc) standards

October 4, 2005WSRP Technical Committee6 Federated Portals Would there be significant performance benefits to allowing user interactions to go directly to a Producer for some portion of an application rather than requiring all interactions be tunneled through the Consumer? How would sufficient context flow upon transition between the portals, particularly when they run on different platforms?

October 4, 2005WSRP Technical Committee7 Multi-tiered aggregations Example: Base content providers offer streaming video of a race or driver stats or chat facilities, etc Intermediary wraps up a collection of base providers, adding coordination and various Consumer resources Final portal offers the intermediary along with other user preferred portlets

October 4, 2005WSRP Technical Committee8 Impacting multiple places on page Mobile device portals (Vodaphone presentation) … particularly for VoiceXML XForms Tabbed pages (particularly with AJAX) …

October 4, 2005WSRP Technical Committee9 Proprietary markups Any issues incorporating these (e.g. URL rewriting)? Identifying those without unique mimetypes (e.g. cHTML)

October 4, 2005WSRP Technical Committee10 Security WSRP security concerns have been explored and the decision made to just guide users in leveraging other standards Open question regarding policy standards to help with configuration as these are not very far along the standardization process

October 4, 2005WSRP Technical Committee11 Load balancing All WSRP features need to be aware of issues related to both the Producer and Consumer potentially executing on a cluster of machines. In addition, emerging concepts of a service bus need to be explored relative to WSRP