-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Friday, August 12, 2005 7:48 PM
To: Tomcat Users List
Subject: Re: Tomcat and the HttpServletRequest Object
From: Hassan Schroeder [EMAIL PROTECTED]
:snips from: http://www.w3.org/TR/html401/interact/forms.html#h-17.13
So it seems the HTML
Jeff Grangier wrote:
Would anyone in the Project Management Committee, Advisory board, or the
committer group acknowledge that this bug is understood and will be
considered in the next releases of Tomcat?
The issue is understood.
This is not a bug, since there is no spec violation. Given the
Jeff,
You still haven't given a rationale why you *need* the parameters presented in
a specific order (even though the brower's supposed to produce that result).
I've worked with a set of generic form processing servlets and never had the
desperate need to know the order upon receipt; if I'm
I see nothing in the specification that specifies the order of the elements
returned in the enumeration.
Why do you think this is a bug?
George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
-Original Message-
From: Jeff Grangier [mailto:[EMAIL PROTECTED]
in this upgrade?
Thanks,
Jeff
-Original Message-
From: George Sexton [mailto:[EMAIL PROTECTED]
Sent: Friday, August 12, 2005 12:40 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat and the HttpServletRequest Object
I see nothing in the specification that specifies the order of the elements
'
Subject: RE: Tomcat and the HttpServletRequest Object
Hello George,
I will consider it an ehancement if it is not in the
specification. Adding a
logical order to the list makes it much easier to manage dynamically.
Otherwize, any programmer will have to create their own
proprietary indexing
From: Jeff Grangier [EMAIL PROTECTED]
Each Element out the getParameterNames enumeration used to be ordered
based
on the html form layout posting the data (using iPLanet). But, after the
migration the fields are coming in random order when I try to loop through
the fields dynamically. . .
: George Sexton [mailto:[EMAIL PROTECTED]
Sent: Friday, August 12, 2005 1:46 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat and the HttpServletRequest Object
Even if I were to write this as an enhancement, I can tell you from past
experience it would be rejected out of hand by the committers
I have the same bloody problem. The application is a generic form handler that
e-mails the form values. Most (all) of the clients expect the values to be in
the same order as the form itself.
I question the requirement to improve performance on request parameters. Vast
majority of the
The recognition (and so far, little acceptance) that form fields will not be
sent in a guaranteed order by a browser, and never mind that, because even
if your browser does, the container doesn't guarantee an order either... is
from Beginner's Servlets. But maybe I only think that because the
From: Bhupinder Dhillon [EMAIL PROTECTED]
I have the same bloody problem. The application is a generic form handler
that e-mails the form values. Most (all) of the clients expect the values
to be in the same order as the form itself.
You are depending on arbitrary browser behavior. As far
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Friday, August 12, 2005 4:07 PM
To: Tomcat Users List
Subject: Re: Tomcat and the HttpServletRequest Object
From: Bhupinder Dhillon [EMAIL PROTECTED]
I have the same bloody problem. The application is a generic
Wendy Smoak wrote:
You are depending on arbitrary browser behavior. As far as I can tell,
there's nothing preventing me from writing a browser that, say,
alphabetizes the request parameters before sending them to the server.
well.
:snips from:
From: Hassan Schroeder [EMAIL PROTECTED]
:snips from: http://www.w3.org/TR/html401/interact/forms.html#h-17.13
So it seems the HTML specification *does* require the parts be sent
in particular (source) order.
Thanks! I was using the wrong search terms-- 'parameter' instead of
'control
14 matches
Mail list logo
