Great! Yes, I will take this on, and I will also see about getting the change into SocketAcceptor. I'll let you know if I need any help.
Thanks -Greg On 4/5/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
On 4/5/07, Greg Duffy <[EMAIL PROTECTED]> wrote: > Here's one possible use case: I have just one processor thread and no thread > pool. I want to unbind from within an IoHandler method (messageReceived, > sessionIdle, etc), but currently we wait for the unbind to finish. Doesn't > this automatically create a deadlock? I.e., waiting for an unbind in the > thread that services the unbind request. > > I could create a separate Executor and submit tasks that do the actual > unbind, but if we provide Bind/UnbindFuture, it simply turns into > IoAcceptor.unbind() vs. IoAcceptor.unbind().join() ... > > I guess it's the same for binding a new IoAcceptor from the processor > thread. A lot of applications use ephemeral ports, and that is where this > issue will come up. > > Let me know what you think, or if I don't understand something about this :) Aha! Sounds reasonable to me. Are you going to work on the change? It would be great! Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
