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: Re: [wsrp] extendedURLParameters question



I'm not so sure this stands in the way. There is actually a pair of statements which should not be separated from each other, namely:

Consumers MUST NOT resend a particular set of wsrp-extra:extendedURLParameters on later invocations of WSRP defined operations. Portlets needing any of the supplied data in order to properly rerender their markup are responsible for storing that data between requests.

The intent of the discussion that lead to the insertion of these statements was to tightly define how the Consumer processes these extra items from a URL and then leave it to the Portlet/Producer to leverage this well-defined behavior. In the case of the ID parameter you are considering mapping, it would be quite reasonable for the Producer to store the last received ID parameter and resupply this to the Portlet if one is not received from the Consumer. The only downside I see to such a mapping is that the missing case could not be used to signal render the Portlet's full markup, but rather a value would need to be assigned to this rendering as well. If this is not feasible, perhaps we should take a closer look underlying use case again.

Rich



Subbu Allamaraju <subbu@bea.com>

09/25/2006 09:03 AM

To
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



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