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: spec-2.0-draft-05: RuntimeContext: public parameters question

what is the intended behavior of public params across requests? The spec 
currently states that the portlets should not store these params as the 
consumer will provide them in each request. Does that mean that the 
portlet can count on getting this param from a specific producer after 
the first time it receives this param?
How can the portlet find out which params the consumer will support? E.g 
if the portlet knows that the consumer will not provide the zip code it 
can output a msg and a link to the edit mode to preset some zip code. 
When it knows that the consumer provides the zip code but the current 
request is lacking it the portlet can output some warning that the zip 
code was not available.


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