implementation of blocking input

[Norman Maurer]

BTW, if you have something better in-mind you can also fork it, write
a patch and then issue a pull request.

It's opensource ;)

Bye,
Norman


2011/10/19 ljohnston <johnstlr at yahoo.co.uk>:
> Hi Bill
>
> I remember you making this point previously.
>
> Here's a really horrible suggestion that could break in future.
> NioSocketChannel stores the current NioWorker as a package protected member.
> NioWorker also stores the current selector as a package protected field.
> Could you create a class in a package that parallels the
> org.jboss.netty.channel.socket.nio package and expose the selector. The
> relevant fields are
>
> NioSocketChannel.worker
> NioWorker.selector
>
> Perhaps raise an enhancement request to provide a proper way of doing this?
>
> Cheers
> Lee
>
>
> bburke wrote:
>>
>> I don't want to do context switching between a reader thread and the
>> application as it just doesn't perform as well as real, blocking I/O.
>>
>
>
>
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/implementation-of-blocking-input-tp6902613p6907929.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>