On Mon, 17 Apr 2000 15:08:47 -0700, Jason Hunter wrote:
> setCharacterEncoding() sounds good. Have it change how parameters
> are read and how the Reader is constructed. Leave it to the programmer
> to determine what a client's encoding is since there's no standard way,
> and anything we build seems likely to interfere with the various content
> creation practices.
Exactly! Thank you for the understanding and support :)
> I think I proposed this in a previous discussion or at least endorsed
> it, but some didn't like that it didn't solve the whole problem. If
> someone has a good proposal for solving the whole problem, let's
> hear it.
What do you mean by the whole problem? Do we really need this kind of a
solution? As far as I can see, the problem does not even exist for the
majority of developers. But the others could use a new infrastructure,
since it would be just a normalization of a remedy they were already using
or were going to use.
Sincerely,
Dmitry.
___________________________________________________________________________
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
