Re: Async IO / signals

I think you are going about this entirely the wrong way. There are two propper ways, that I can see:

Rewrite your program to work as an event loop: call select($rbits,$wbits,$ebits,0) to find FDs ready for I/O, and process them
Write two threads: One does select($rbits,$wbits,$ebits,00.1) </code>(Note the non-zero timeout), which only makes note of which filehandles are ready for I/O, and leaves the information somewhere for the main process to find.

If the "process I/O buffer" is an operation with a guaranteed upper time limit, the first option is probably preferable.

Comment on Re: Async IO / signals Download Code

Replies are listed 'Best First'.
Re: Re: Async IO / signals by powerman (Friar) on Apr 19, 2004 at 14:17 UTC
Event loop is of course good thing... when it possible. But it isn't always possible: sometimes I need to do very long calculations inside event loop and this will result in FDs timeout and error. Also event loop isn't good idea if "process IO buffer" isn't main task of this program. Threads... hmm... not in perl. At least - not current iThreads. They are too slow and use too much memory. So I wonna to make safe ASYNC IO without threads using SIGNALS as was described before.	[reply]

Replies are listed 'Best First'.

Re: Re: Async IO / signals
by powerman (Friar) on Apr 19, 2004 at 14:17 UTC

timeout

safe

[reply]