Re: Re: (5) : UDP and IO::Socket

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

Comment on Re: Re: (5) : UDP and IO::Socket

Replies are listed 'Best First'.
Re: (7) : UDP and IO::Socket by agoth (Chaplain) on Jan 18, 2002 at 14:38 UTC
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( sleep.pl ) 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..	[reply]

Replies are listed 'Best First'.

Re: (7) : UDP and IO::Socket
by agoth (Chaplain) on Jan 18, 2002 at 14:38 UTC

Ah, just thought, is your server waiting for system( sleep.pl ) 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..

[reply]