🚀 go-pugleaf

"John McGrath [TeamB]" <ng-b@JPMcGrath.net> wrote in message
news:MPG.1816ea6e9f26b40e98ba95@newsgroups.borland.com...
> On Sun, 13 Oct 2002 17:51:10 +0100, Owen Green wrote:
>
> > Any (easy) home grown solutions look like they'd suffer from
> > the same frailties as all the old deprecated JDK1.x conversion
> > methods, as they'd rely on assumptions about the character
> > encoding.
>
> The java.nio package in Java 1.4 has new classes for dealing with
> encoding.  I have not tried them, but this may be what you need.

Should have mentioned that given that it's going towards a public
framework I was trying to keep it to within 1.3 compatibilty - limiting
it to 1.4 would probably reduce take-up.

I really can't see /why/ InputStreamReader has to over read though - I
understand that's for efficiency, but it would be nice to be given the
option.*

The Jetty servlet engine seems to have something that deals with this,
so I'm looking at their code to see if it provides any insight.

Thanks for the suggesstion,
Owen

*Unless I misunderstand it's behaviour. But, AFAICS, it will just read
in it's default buffer (8k) every time it fills, which knackers you if
you have arbitary textual and binrary content in the same stream.