Re: [wsrp] extendedURLParameters question

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

Unfortunatly I haven't been part of the discussion last week, so I might
miss the context.

However this parameter is scoped to the request only, and by request scope
I mean the WSRP request.
We don't have a definition of what the user interaction scope is per se.
And we have no tie of the operation considering the preservation of state
between these.

These parameters are mainly intended to allow browsers/client side
scripting to extend the URL params (if the Consumer portal is capable of
handling it) and pass them back to the portlet.
This can only be request scoped. The Consumers have no idea about the
intended semantics of the params. There are certainly use cases were the
portlet expects these to be request scoped only.
It seems also very natural for me, since all request params (extended or
not) are request scope.

It seems we're trying to include the user requet life time in the very last
minute again.

Mit freundlichen Gruessen / best regards,

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


                                                                           
             Subbu Allamaraju                                              
             <subbu@bea.com>                                               
                                                                        To 
             09/25/06 03:03 PM         OASIS WSRP TC                       
                                       <wsrp@lists.oasis-open.org>         
                                                                        cc 
                                                                           
                                                                   Subject 
                                       [wsrp] extendedURLParameters        
                                       question                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




I have a question regarding sending extended URL parameters.

Is a consumer allowed to send these parameters on more than one markup
operation during the scope of the client request that included these
parameters?

In particular, if a blockingAction URL contained extended URL
parameters, is it valid for the consumer to send these parameters on the
following requests during the scope of the same client request

- pbia
- handleEvents (only to the portlet that initiated the request)
- getMarkup (only to the portlet that initiated the request)

The statement "Consumers MUST NOT resend a particular set of
wsrp-extra:extendedURLParameters  on later invocations of WSRP defined
operations" in Sec 12.2 seems to be preventing this.

During last week's interfaces call, it was pointed out that the request
ID notion for the ajax discussion can be mapped to extended URL
parameters, and this conformance statement stands in the way. Is there a
reason not to relax this statement by adding "beyond the scope of the
current request".

Regards,
Subbu