> The problem is that some Fitler may decide to detach a ByteBuffer and
> not return in to WorkerThread.
> Actually we need to check (recreate if required) BB each time before a
> new task to be executed on a WorkerThread.
> So create BB just once, when Thread is going to be created will not work :(
Good point. It also shouldn't be a threadPool's resposibility to manage
the byteBuffer. Image I have a single threadPool which I use for
multiple applications (also grizzly). With the current design, each
thread of this pool will get a byteBuffer at some point in time.
A better way is to detach the byteBuffer from a thread when is it not
needed and re-attach it again once a certain thread is going to do some
work for grizzly.
Seb