Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

Re: Re: Re: Re: UDP and IO::Socket

by toadi (Chaplain)
on Jan 16, 2002 at 14:52 UTC ( #139171=note: print w/replies, xml ) Need Help??

in reply to Re: Re: Re: UDP and IO::Socket
in thread UDP and IO::Socket

See where you are getting at, but the documentation if IO::Select is to sparse to understand your example. Can you give some more info?

My opinions may have changed,
but not the fact that I am right

Replies are listed 'Best First'.
Re: (5) : UDP and IO::Socket
by agoth (Chaplain) on Jan 16, 2002 at 15:35 UTC
    As I understand it, (i.e. I'm not positive), calling IO::Select on a list of handles returns a list of waiting filehandles ( in this case sockets ), and in your case as you are not writing out, the only waiting handles will be readable handles, zero one or many.

    In the loop, you can then iterate over any readable handles that have been assigned to @read by calling IO::Select, doing with as you wish. As you're using UDP, you don't need to worry about the connection unduly, nor have to close or give a response as the client doesn't wait for anything so you can just discard the client request as you don't want to sleep.

    In the code below, the udp socket is added to the list of known waiting input readers,
    IO::Select can accept many handles, the server enters an infinite loop, reading any waiting handles in and clearing the queue. It is important to get the non-blocking stuff in so that the server will skip over any hung items, though whether this non-blocking stuff actually works for UDP,( this was munged from a UDP/TCP combined server) and the IO::Select->select ( x,x,x, 1) enforces a 1 second sleep I think.

    HTH, I only posted briefly yesterday 'cos I was in a rush, but hope this is clearer..

    use POSIX; use IO::Socket; use IO::Select; my $udp = new IO::Socket::INET(LocalAddr => $interface,'LocalPort' +=> $port, 'Proto' => 'udp') or die $!; my $sockin = new IO::Select; my $sockout = new IO::Select; my $sockerr = new IO::Select; $sockin->add($udp); my ($read, $write, $err) = ([],[],[]); while(1) { ($read, $write, $err) = IO::Select->select($sockin, $sockout, $soc +kerr, 1); for my $sock (@$read) { my $data; $sock->recv($data, 1024 * 64, 0); next if $! == EAGAIN() || $! == EWOULDBLOCK(); #---- $! is po +pulated by IO::Socket # client request in $data ---- process as you want } for my $sock (@$write) { # not important } for my $sock (@$err) { # clean up any errors } }
      his will not wait for individual actions to complete and will allow you to close incoming reads

      And how can I close the incoming reads as longh as sleep is running. I don't want them to be in the queue as long as sleep is running. SLeep may only be activated by a request from a client after sleep is finished!

      My opinions may have changed,
      but not the fact that I am right

        Being UDP you dont need to respond to them, read in the message, ignore it if sleep is running, then close that handle, therefore your queue should be empty.

        Ah, just thought, is your server waiting for system( ) to return ?. If so replace the system call with a fork (and waitpid) or a fork and exec, so that the main server can continue processing requests and the sleeping can be performed independently..

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://139171]
and dust plays in a shaft of sunlight...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (3)
As of 2018-05-26 02:56 GMT
Find Nodes?
    Voting Booth?