Godmar Back wrote:

[...]  Every call results in a new
> converter object being newinstanced, just to convert a bunch of bytes.
> (The new converter was one of the changes done to make the
> charset conversion thread-safe.) 
[...]

And why exactly default converter could not be cached and same instance
used for all conversions ? I think it is stateless class, so it should
be safe to enter same object method from various threads with all state
on stack.

Artur

Reply via email to