https://issues.apache.org/bugzilla/show_bug.cgi?id=55576

--- Comment #3 from corythearchit...@outlook.com ---
Thomas, thank you for your rapid evaluation and response on this matter.

The general use case is the servicing of a request in which the order of
parameter evaluation is significant.

http://host/resource?country=CA&postalcode=N7T5R4

Let's assume this is in context of a general infrastructure that evaluates each
parameter in the order received (field validation being just one example of
potential triggers). postalcode validation is dependent on the value of
country.

The specific scenario I am currently dealing with is porting a web service
implementation from ASP/IIS to Java/Tomcat. The Microsoft
IRequestDictionary.QueryString implementation respects order of insertion,
while Tomcat scrambles the order as a result of the backing HashMap collection. 

I respect your position that there is no explicit specification of the
server-side evaluation of HTML parameters.  However, I also see no significance
to the client-side specification of parameter order beyond the implication that
the ordering is also significant to the processing server that consumes it.
What other purpose could such an ordering possibly serve?

Assuming equivalent performance, what portability issues could arise from a
MORE determinate collection implementation? If anyone is currently relying on
the iteration order of the existing HashMap implementation,
a) they are in for a surprise anyhow, and
b) the ServletRequest interface, unfortunately, provides no guarantees, relying
on the generic Map and Enumeration interfaces, both of which defer to the
implementation for behaviour in this regard.

This decision could only be interpreted as an improvement in compliance (with
the HTML specification).

-- 
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

Reply via email to