https://issues.apache.org/bugzilla/show_bug.cgi?id=55576
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
OS| |All
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
The Servlet specification does defer to W3C for all HTML matters.
The text quoted above regarding ordering only applies when
application/x-www-form-urlencoded is being used. Strictly, it applies only to
the order that the client provides the data. It could be argued that if the
client is required to provide the parameters in order in this case then the
getParamererXXX() methods should respect that order. Further, if the order
needs to be maintained for this one case, it is easier to maintain it for all.
However, there is nothing that I can see in either the Servlet or HTML
specifications that strcitly requires the Servlet API to present the parameters
in the same order as they were received.
There is no major performance difference (I am aware of) between HashMap and
LinkedHahsMap so I am not against making this change but neither (at this
point) do I really see the need for it. One concern I do have is that given
that there is not a requirement for this, other containers may not implement it
and that could cause portability issues.
I am curious as to the use case that supports it. Can you elaborate on why it
might be important for the parameters to be returned in the same order as they
appear on the form.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
