Frank Carver wrote:
> Section 5.1, para 3.
>
> "All form data from both the query string and the post body are
> aggregated into the request parameter set. The order of this
> aggregation is that query string data takes precedence over post body
> parameter data."
>
> Although better than previous releases, this is still not fully clear.
> What does "takes precendence" actually mean? Consider the following case:
>
> query: a=hello
> post: a=goodbye a=world
>
> possible parameter set: a=(hello, goodbye, world)
> (ie "takes precedence" means appears first in the list)
>
> possible parameter set: a=(hello, world)
> (ie "takes precedence" means overwrites first post argument)
>
> possible parameter set: a=(hello)
> (ie "takes precedence" means overwrites all post arguments)
>
> I really hope (and suggest) that my first answer is the correct one,
> but it certainly needs clarification in the text.
>
Your first answer (values are merged, with the ones from the query string
first) is the intended meaning, and is the way that the reference
implementation does this.
Craig McClanahan
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
