------- Additional Comments From [EMAIL PROTECTED] 2005-04-13 06:00 -------
Tony, yes, now that we are using the DNS ID to match up replies to queries there
is no reason to use more than one socket for that purpose. Where was your
single-socket-with-DNS-ID vision when we were trying to figure out this bug five
months ago? :-) What we have now is the simpler solution to getting the existing
code to work. Going to a single socket will take some work to get the socket
available to both Dns.pm and URIDNSBL.pm, or else use two sockets in all,
closing it or them at the right time, etc. As always, patches are gratefully
accepted.
I posted to the list a recipe detailing exactly how to do this. I didn't have code to post as it was implemented in a completely different framework, but it should be really easy to follow the recipe to create something yourself.
Oh, and the recipe means you only ever use one socket, even if called from two different classes.
I don't post to this list very often, so it should be trivial to dig up.
Matt.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
