[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gawk] Issue with read timeout on TCP socket

From: Andrew J. Schorr
Subject: Re: [bug-gawk] Issue with read timeout on TCP socket
Date: Thu, 30 May 2013 09:53:32 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, May 30, 2013 at 02:21:29AM +0300, Serge A. Zaitsev wrote:
> Which is always true after the timeout, because IOP_AT_EOF flag is always
> set if select() returns -1 (which is select() error, e.g. timeout).
> For my case I removed the line io.c:3351 (I'm talking about 4.1.0 sources
> form the tarball) and that helped.
> I'm sure this will break other things in Awk, so could you please look for
> a proper solution?

You seem to be correct.  If the timeout expires, it is an error condition.
There is currently no capability to read again after a timeout expires.

It would be really nice to add a "select" extension to gawk to solve
this type of problem and enable I/O multiplexing.  I don't think the
existing extension API provides enough features for this to be implemented.

I think we need an API hook to call the getredirect function.  Arnold, do you
have any thoughts on this?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]