[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp] comment regarding interactionState
The suggested work-around for forms with method=GET is to use "/" (i.e. paths) instead of query strings. However, this has problems (see tomorrow's agenda) with our advice to URL encode values. For example, when placing interaction state on URLs. Our failing is to rely on URL encoding when any arbitrary URI scheme may need to be supported.
A second related issue is that URL templates (unless the consumer also re-writes the templated URLs) don't allow lengthy interactionState to be moved out of URLs. So placing URL params (such as interactionState and navigationalState) into consumer side storage or into hidden fields (i.e. not on the URL) is not possible with only direct URL templates.
In effect, either an extra consumer side parsing is required or forms with method GET don't get supported. One thing we could do is to make templates optional (even if producers set doesUrlTemplateProcessing=true).
regards,
Andre
-----Original Message-----
From: Subbu Allamaraju [mailto:subbu@bea.com]
Sent: 04 June 2003 02:40
To: wsrp@lists.oasis-open.org
Subject: Re: [wsrp] comment regarding interactionState
> Now, if the portlet were creating a form, and the action was associated
> with the submit (POST) for the form, then of course it could specify no
> query params in the URL...so that, if it wanted interactionState
> associated with the form action, it would have to embed it as a hidden
> field.
You mean, a form with a GET?
Subbu
You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/wsrp/members/leave_workgroup.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]