==================BEGIN FORWARDED MESSAGE==================
> From: Eugen Kuleshov <[EMAIL PROTECTED]>
> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Subject: Character encoding problem review
Hello.
Please forward this reply to servlet-interest. I'm having troubles with
mail currently.
---------------------------------
Jason Hunter wrote:
> > Isn't that important? Why should you massage the data yourself
> > every time, if it could be massaged for you properly? :)
>
> The new API call doesn't let you do anything you couldn't do before
> with minimum effort. Therefore it isn't that important when compared
> to actual new features, things that let you do something you couldn't
> do before. That doesn't mean I wouldn't support it being included.
> It's on the list of things to consider for 2.3 and my gut instinct is
> that some form of the method will merit inclusion -- it has a good
> benefit to complexity ratio. :)
Dont' forget that it's not only new API call for setting encoding.
but olds calls:
HttpUtils.parsePostData( int len, ServletInputStream in)
HttpUtils.parseQueryString(java.lang.String s)
must be deprecated and new two must be added
HttpUtils.parsePostData( int len, ServletInputStream in, String
encoding)
HttpUtils.parseQueryString(java.lang.String s, String encoding)
then just this methods must be used for parsing request parameters.
Eugen Kuleshov.
===================END FORWARDED MESSAGE===================
DP: I think, that there's might be easier just to use a single parameter of
HttpServletRequest instead.
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
