R: Non-DNS async support

2007-09-21 Thread Giampaolo Tomassoni
> -Messaggio originale- > Da: Mark Martinec [mailto:[EMAIL PROTECTED] > > Giampaolo, > > > Well, I have 3.2.1 and the excerpt from AsyncLoop.pm was from there. > > But anyway, how is supposed to be set the timeout value of a non-DNS > query? > > The current code in trunk is able to speci

R: R: Non-DNS async support

2007-09-20 Thread Giampaolo Tomassoni
> -Messaggio originale- > Da: Mark Martinec [mailto:[EMAIL PROTECTED] > > Giampaolo, > > > Not really (at least not in the current trunk I'm looking at). > As long as there are any (non timed-out) requests in %$pending, > it does not terminate, even if poll returns empty-handed. Well, I

Re: R: Non-DNS async support

2007-09-20 Thread Justin Mason
Mark Martinec writes: > > Almost. One of the biggest problems I see is that one can't register a > > socket with AsyncLoop.pm. Thereby, when DNS lookups are finished, the whole > > loop stops regardless of outstanding non-DNS-based lookups. > > > > See sub complete_lookups in AsyncLoop.pm: > >

Re: R: Non-DNS async support

2007-09-20 Thread Mark Martinec
Giampaolo, > Almost. One of the biggest problems I see is that one can't register a > socket with AsyncLoop.pm. Thereby, when DNS lookups are finished, the whole > loop stops regardless of outstanding non-DNS-based lookups. > > See sub complete_lookups in AsyncLoop.pm: > my $nfound = $self->{m

R: Non-DNS async support

2007-09-19 Thread Giampaolo Tomassoni
> if I recall correctly, most of the code works fine without using > DNS; it's just that most of the code currently *using* it works > with DNS. Almost. One of the biggest problems I see is that one can't register a socket with AsyncLoop.pm. Thereby, when DNS lookups are finished, the whole loop s