Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Order of parameters
Date: Wed, 8 Oct 2003 11:46:06 +0200
Message-ID: <61BAD406AA642745AE1142AF689E8D8E030B25@madocontrol.madocke.local>
Thread-Topic: Order of parameters
Thread-Index: AcONgP7brCaczzzSSxChaYrRZpP4gg==
From: "Martin van Dijken" <mvdijken@madocke.nl>
To: "Tomcat Developers (E-mail)" <tomcat-dev@jakarta.apache.org>

I've been trying to create an automated form handler. This form handler =
could be a lot more effective if the request parameters were in the =
order they were put on the form. Now most browsers send this information =
over HTTP in the order they were found in the form. However, because the =
parameters are in Tomcat put into a Hashtable, the order is lost and can =
never be rebuilt.

First of all, does anybody have a problem with a little code to keep the =
parameters in order?

Second, please comment my proposed solution:=20

The best way I can think of to change this involves creating an =
extension of Hashtable. At the moment a parameter is put into the =
Hashtable, the key is put into an Arraylist. When =
request.getParameterNames() is called, the parameters are returned in =
the order they are found in the ArrayList. This would keep the speed of =
accessing request.getParameter() fast and put a little overhead at =
request creation and getParameterNames.


Martin van Dijken

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org