On Feb 25, 2008, at 12:55 PM, David Connelly wrote:
How about just a variant on bind() that takes a ServerSocket(Channel) rather than an IP/port combination?This is essentially what I had done except I called this new method 'register' rather than 'bind' in order to reflect that the server socket had been previously bound, but either method name is fine by me. I also think this would be the simplest solution in terms of ease of use.
ah, good point. its already bound :)
As Trustin said, we can put it into the core for 2.x, but 1.1.x isjust in maintenance mode until we can get 2.0 out. (realizing the painit causes to continue to have delays). But do post a patch!I understand this is probably too late for 1.1.x so we'll keep using our patched version in the meantime until 2.0 ships. If I file a JIRA issue as Trustin suggests should I include the patch there or should I post it separately?
include the patch in the jira issue please, as there's an important checkbox there that says you're making the contribution under the terms of the ASLv2.
Finally, I also wanted to thank both you and Trustin for the quick response!
thanks for being a user! -pete -- (peter.royal|osi)@pobox.com - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
