> > Sort of a "here's the decoding method I want" flag. I'm not
> > sure you're
> > going to see that added to the servlet spec since the pertinent RFCs
> > just don't make enough guarantees that things like that will always
> > work. But you can of course build a little infrastructure to do it
> > yourself. I showed in the book how to use a hidden charset value.
> > That's been a commonly accepted way to deal with this problem.
> >
>
> If the problem exist and has "a commonly accepted way to deal
> with this problem" why can not it been included in standart API?
Because not everything can, or should, go in an API. If you actually
look at the approach, you'll see it goes beyond what mere methods can
do. To standardize on it would be awfully complicated and heavyhanded,
esp for a solution that isn't guaranteed to always work in the future.
-jh-
___________________________________________________________________________
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
