Re: [gui-dev] Chasing possible memory leaks?

NIO is still a little buggy but once you know which parts work and which don't 
(like for example setSoTimeout() on Sockets created using NIO) it appears to 
cause little problems.

The setSoTimeout() problems make it especially hard to mix NIO with classic IO.

mfg
gregorio

Susheel M. Daswani wrote:

> 
> No doubt NIO is a great alternative - I'm just a little spooked after 
> hearing some NIO horror stories from the FreeNet world.
> 
> Thanks!
> Susheel
> 
> Gregorio Roper wrote:
> 
>> LimeWire is going to need NIO before increasing the number of 
>> connections... NIO rocks!
>>
>>
> _______________________________________________
> gui-dev mailing list
> [email protected]
> http://www.limewire.org/mailman/listinfo/gui-dev
> 
_______________________________________________
gui-dev mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/gui-dev