On Friday, August 20, 2004 3:50 PM, Wiggins d Anconia wrote: > confused about or are attempting to do. IO::Multiplex works at a > lowlevel on filehandles, specifically sockets. Net::DNS::Nameserver is > designed to be a high-level all inclusive server, aka you don't really > have access to the sockets it is using.
That's exactly why I was posting -- I was hoping someone had a different answer :) I shouldnt have limited my query to IO::Multiplex, rather any solution for a non-blocking solution for Net::DNS::Nameserver. > So take two steps back, tell us what you are really doing... then take > one step back and tell us why you chose these two modules, and how you > are thinking they should fit together, and whether you are open to other > suggestions. the example at http://search.cpan.org/~crein/Net-DNS-0.48/lib/Net/DNS/Nameserver.pm (and any other variation) can only handle a single query at a time. I simply want to create a server using Net::DNS::Nameserver that can handle multiple requests, concurrently. I do want to keep Net::DNS::Nameserver as the server, but am open to all suggestions on how to make it non-blocking. My experience with IO::Multiplex has been positive, and thought they could solve the problem together, if they could talk to each other. I should add that I'm not interested in forking off processes to handle concurrency, though; that'd be way too slow and dirty. > This is where I will make a preliminary gamble (or maybe a "blind" bet) > and say POE can do it :-).... I'm looking at it now... thanks again. Jeremy Kister http://jeremy.kister.net/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
