Hi
Ok, I have created a request parameter processing prototype in my whiteboard
[1]:
- Create new "parameters" bundle to reuse request parameter support
independently of the Sling Engine
- Added new ParameterSupport method to retrieve java.util.List of
request parameter name-value pairs (of all parameters extracted)
- Updated to Servlet API 3.0 (still need to make sure that we can also
deploy this on Servlet API 2.4|5 environments
WDYT ?
Regards
Felix
[1] https://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/parameters
Am 16.01.2014 um 23:11 schrieb Alexander Klimetschek <[email protected]>:
> On 16.01.2014, at 02:15, Bertrand Delacretaz <[email protected]> wrote:
>
>> This looks like a mini language, so I'd say using multiple parameters
>> for that is a bad idea, I'd rather have
>>
>> commands="layer 0 ; img mypic.jpg ; rotate 10 ; layer 1 ; img anotherpic.jpg"
>>
>> or something like that, as a single parameter.
>
> Well, maybe, but I can’t change that.
>
>> I'm not even sure if proxies and other HTTP intermediaries are
>> supposed to keep the order of parameters, not having to rely on that
>> is certainly safer.
>
> Yes they are, the URL is fixed and the response body (for a POST) as well.
>
> As I referred to above, the HTML spec clearly says that the order is
> important and based exactly on the order of form fields in the HTML.
>
> The problem is only introduced by the java servlet API that apparently didn’t
> read the spec.
>
> Cheers,
> Alex
