I am no expert, but if I had to take a guess (and  I don't :-) )  I
would go with historical flub.  The getParameterValues() appears very
early on in the servlet spec, possibly before Enumeration became en
vogue.  On the other hand, the actual object being returned is a set of
String values, and since Java does not implement type specific
collections yet, it may be clearer as is.

David M. Karr wrote:

I'm curious what the rationale was for certain collection return types in some
servlet (2.3) specification methods.

All of the ones I found in the spec return Enumeration, except for one, which
returns an array of String.  What was the rationale for the one oddball?  I can
see that all the others get a list of "names" and the odd one returns a list of
"values", but I don't see how that would make a difference.

These are the ones I found (I may have missed some):

Enumeration ServletRequest.getAttributeNames()
Enumeration ServletRequest.getParameterNames()
Enumeration ServletConfig.getInitParameterNames()
Enumeration HttpServletRequest.getHeaderNames()

String[] ServletRequest.getParameterValues()

--
===================================================================
David M. Karr          ; Java/J2EE/XML/Unix/C++
[EMAIL PROTECTED]   ; SCJP

___________________________________________________________________________
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

___________________________________________________________________________
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

Reply via email to