Re: [wsrp] spec-2.0-draft-05: RuntimeContext: public parameters question

[Richard Jacob <richard.jacob@de.ibm.com>]

Stefan,

I think having the values per request is valueable.
The reason for this is that in such a case the Conusmer doesn't have to
deal with the portlets "caching" semantics at all and that we don't need to
provide support for that in the protocol (and allows stateless Producers
btw.). I could imagine very different places where a portlet could store
these things (WSRP session, HTTP session, DB, navState,...).
I think portlets don not really need information on what will eventually be
provided by the consumer.
They can discover at runtime and take appropriate action as you describe it
(pop up to enter the data, link to edit mode, etc.).

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Standardization Technical Lead
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com


                                                                           
             Stefan Hepper                                                 
             <sthepper@hursley                                             
             .ibm.com>                                                  To 
                                       WSRP TC <wsrp@lists.oasis-open.org> 
             03/09/2005 08:13                                           cc 
             AM                                                            
                                                                   Subject 
                                       [wsrp] spec-2.0-draft-05:           
                                       RuntimeContext: public parameters   
                                       question                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Rich,
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.

Stefan


---------------------------------------------------------------------
To unsubscribe, e-mail: wsrp-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: wsrp-help@lists.oasis-open.org