Well, the NIO we're doing right now is more of a load-test. It uses NIO internally, but everything else remains the same (two threads per connection, etc...). We're going to put out a beta with that, just to work out the bugs and idiosyncracies with the NIO classes themselves. Then we'll work on reworking the core to use a single thread and use NIO as it's meant to be used, which will drastically reduce the memory footprint, etc.