Differentiate synchronous and asynchronous error of an AIO operation
Zhong Yu
zhong.j.yu at gmail.com
Tue Jun 14 16:51:35 PDT 2011
Thanks Alan, I think I have a better understanding of fixed thread
pool configuration. If a handler is potentially blocking, it has to
dispatch the real work to another thread, but that's not hard. Under
this configuration it's easy to add flexible threading strategies.
I still don't have a clear understanding of the official behavior of a
group with user-supplied executor. Reading the implementation doesn't
help - it got me more confused. Well I'll steer clear from them. And
the default group too.
On Tue, Jun 14, 2011 at 2:01 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> For example on editions of Windows that don't support thread agnostic I/O
> then we have to initiate the I/O operations on pooled threads and so a task
> may be executed to initiate the I/O operation.
Any reason there can't be a fixed internal thread for these I/O requests?
- Zhong Yu
More information about the nio-dev
mailing list