On 6/16/06, Pete McKinstry <[EMAIL PROTECTED]> wrote:
I created my own SocketAcceptor class based on the default one that can handle binding to an undefined port number (either via null inet address or a port of 0). It's almost exactly the same except for providing a callback mechanism for notification of the port chosen. I would prefer returning a future from the bind() method that provides access to the chosen address, but since I'm not able to mess w/ the method signature, I chose a callback instead. I would also have rather extended the current SocketAcceptor to add this feature, but so much of the impl was private that i really couldn't re-use it.
Could you explain your use case more in detail? It's my first time to see this kind of requirement. Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP key fingerprints: * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
