extendedURLParameters question

[Subbu Allamaraju <subbu@bea.com>]

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