[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907139#comment-13907139
]
Alexander Klimetschek commented on SLING-3403:
----------------------------------------------
I guess the "Util" class now being a full configurable component should get a
different name then - or refactored, so the configuration is on an existing
component/service such as SlingMainServlet (although that one might be a bit
bloated with configuration then).
> Improve Parameter Support
> -------------------------
>
> Key: SLING-3403
> URL: https://issues.apache.org/jira/browse/SLING-3403
> Project: Sling
> Issue Type: Improvement
> Components: API, Engine
> Affects Versions: Engine 2.2.10, API 2.5.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Engine 2.2.12, API 2.5.2
>
>
> As discussed on the dev list [1], Sling's request parameter support should be
> extended and improved:
> * Provide list of request parameters in the order specified in the request
> (the Servlet API does not define the order and servlet containers may or may
> not respect the order in the parameter map; but there is no official API to
> get the list of request parameters in the actual order as defined on the
> request)
> * Support Servlet API 3.0 style multipart/form-data requests
> * Make sure request parameters are uniformely supported on all servlet
> conainers with respect to character encoding and size restrictions.
> As a corollary to Servlet API 3 support for request parameters, we might also
> want to extend the ServletContext API to implement the Servlet API 3 methods
> (even though, most will just throw)
> [1] http://sling.markmail.org/thread/ysz5sxpb6wkuelzd
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
