Re^3: UDP Client Multiple servers

That's not really a good idea. You could just set timeout option on the socket after creating it:

use Socket qw(SO_RCVTIMEO);
use POSIX qw(:errno_h);
...;
my $timeout = pack 'L!L!', $sec, $usec;
$handle->sockopt(SO_RCVTIMEO, $timeout);
...;
my $res = $handle->recv(...);
unless(defined $res) {
    if($! == EAGAIN or $! == EWOULDBLOCK) {
        say "time out";
    }
}
[download]

Comment on Re^3: UDP Client Multiple servers Download Code

Replies are listed 'Best First'.
Re^4: UDP Client Multiple servers by brap (Pilgrim) on Oct 12, 2012 at 13:18 UTC
Does the `Timeout` parameter to IO::Socket::INET`->new()` have the same effect as the `sockopt()` method? Maybe another WTDI.	[reply] [d/l] [select]
Re^5: UDP Client Multiple servers by zwon (Abbot) on Oct 12, 2012 at 14:26 UTC
Not really, despite documentation for IO::Socket::INET says "Timeout value for various operations", `Timeout` parameter is only used by `connect` method of IO::Socket, it doesn't affect `recv` in any way.	[reply] [d/l] [select]
Re^6: UDP Client Multiple servers by brap (Pilgrim) on Oct 12, 2012 at 14:45 UTC
Huh! Good to know. Thank you zwon++	[reply]