On Aug 25 12:08, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > I don't have an answer to this problem yet.
> >
> > Can we use send(sock, "", 0) to reenable FD_WRITE, perhaps?
>
> Can't it just be assumed that the socket is _always_ writeable _unless_ the
> last send() failed?
> In other words, try to always send() if it did not fail before. If it did,
> only send() after
> FD_WRITE was returned in the event mask.
You're looking from the application perspective, but as the underlying
library we don't have the application under control. The application
can rightfully expect POSIX-like behaviour from select(2), and *that*
means, it can expect select(2) to return a socket as non-writable if the
internal buffer is full, *before* it calls send:
while (...)
{
/* send as long as we can, otherwise do another job in the meantime */
while (select (..., <zero timeout>))
send (<blocking>);
<do something else>
}
Corinna
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
