2008-02-25 (월), 07:52 -0800, peter royal 쓰시길: > On Feb 24, 2008, at 6:56 PM, David Connelly wrote: > > Unfortunately, the SocketAcceptor bind() method not only binds the > > server socket but starts > > listening on the server channel immediately as well, which prevents > > prebinding of the ports. > > > > Our temporary workaround has been to add a new 'register' method to > > SocketAcceptor so our application can create and bind the > > ServerSocketChannel as root, setuid to the zimbra user, then call > > 'register' > > to allow MINA to start listening on the server socket. > > How about just a variant on bind() that takes a ServerSocket(Channel) > rather than an IP/port combination?
It breaks the abstraction of the API IMO, because we don't assume that we always use ServerSocketChannel. We could add such a method to NioSocketAcceptor only, but this will give compilation errors to users when they switch to other transports. -- Trustin Lee - Principal Software Engineer, JBoss, Red Hat -- what we call human nature is actually human habit -- http://gleamynode.net/
signature.asc
Description: This is a digitally signed message part
