OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Additional use cases for issue #44 (set new public params)


Hi,
I've some use cases that may be a good match for the ability to set new 
public parameters by the producer and to encode public parameters in 
URls by the producer.

1. displaying content based on a specific product id:
- Portlet A allows to select a product from a list
- User clicks on a specific product
- Portlet B renders details of this product
- Portlet C renders currently available number of items on stock for 
this product
- user wants to bookmark this result in order to come back to product 
tomorrow

implementation with events:
Portlet A encodes the customer selection URLs as POST action links
Portlet A receives a performBlockingInteraction call
Portlet A returns event productID=10
Portlet B receive a blocking handleEvents call for productID=10 and 
returns new navigational state
Portlet C receive a blocking handleEvents call for productID=10 and 
returns new navigational state

implementation with public params:
Portlet A encodes the product selection URLs as GET render links with 
the productID as public param
Portlet A receives a render call with the public param productID=10
Portlet B receives a render call with the public param productID=10
Portlet C receives a render call with the public param productID=10

which would be much more efficient and also consistent with the W3C 
architecture as links that do only change view state should be encoded 
as GET links.


2. display content based on a specific customer id

3. display content based on the selected state of a map
portlet A displays a map of USA
portlet B displays information on the selected state (# people 
registered, capital, ...)
portlet C displays all IBM labs in that state

and many more.


This would allow to have some gobal navigational state that can be set 
via URLs by portlets. Also portlets may want to set new public params as 
a result of an blocking interaction or a handle event call.


What do you think?


Stefan



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]