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?
Thank you, Jeff Grangier Founder & Chief Architect YourWebPro Inc. (847) 454-8000 -----Original Message----- 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 specification *does* require the parts be sent > in particular (source) order. Thanks! I was using the wrong search terms-- 'parameter' instead of 'control name' and so I never found that. At which point I assumed the specification was silent on the matter and I could do whatever I pleased. :) So I stand corrected on the browser behavior part. > But it has nothing to say about what *processing agents* do with 'em. > And if the servlet spec *doesn't* demand that the parts be stored and > made available in that same order... Assuming enough people can be convinced that this is broken, there's where the "fix" needs to be applied. Until the Servlet specification says that the order of request parameters must be preserved, Tomcat is free to do whatever it wants with them. Greg Murray (the Servlet specification lead) has asked for input on what we'd all like to see in the next version, so here's a chance to comment: http://weblogs.java.net/blog/gmurray71/archive/2005/07/got_servlets.html You can also get involved with the JCP: http://www.jcp.org/en/home/index -- Wendy Smoak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
