On Mon, 12 Mar 2007 16:02:11 +0100
"Lluís Batlle" <[EMAIL PROTECTED]> wrote:
> Oh, of course you're right. I was inside too much layers to think of
> the tcp protocol, and I did not pay attention to it.
>
> Maybe something could be added to the manpage anyway.
>
> The bad thing is that there's n
Wouldn't it be better for all of us that select() doesn't block on
write(), unless there is a socket writting buffer fulfilled? It will
be consistent with the select() specification.
2007/3/12, Alistair John Strachan <[EMAIL PROTECTED]>:
On Monday 12 March 2007 15:02, Lluís Batlle wrote:
> Oh, o
On Monday 12 March 2007 15:02, Lluís Batlle wrote:
> Oh, of course you're right. I was inside too much layers to think of
> the tcp protocol, and I did not pay attention to it.
>
> Maybe something could be added to the manpage anyway.
>
> The bad thing is that there's no way I can use a socket for
Oh, of course you're right. I was inside too much layers to think of
the tcp protocol, and I did not pay attention to it.
Maybe something could be added to the manpage anyway.
The bad thing is that there's no way I can use a socket for writing
using select() if that connection has been half-clos
Hello,
I've found a problem in the select() call. The manpage states:
"those in writefds will be watched to see if a write will not block"
I've tried a select() for write against a closed tcp socket (closed by
the other side), and the select call _blocks_.
Any write() call to that socket will _
5 matches
Mail list logo