Dear Corinna,
Thanks for the quick clarification on plans for interruptible connect().
> Btw., switching to non-blocking for the connect/select pair isn't
> actually difficult so I wonder what your problem is.
Cf. Stevens "Unix Network Programming", section 15.3:
"There are many portability problems with nonblocking connnects
that we mention in the examples that follow."
and, after a lengthy discussion of portability issues:
"Unfortunately, nonblocking connects are one of the most nonportable
areas of network programming."
Since my code must run on several flavors of Unix, I hesitate to use
this technique. I suppose I could use it solely for Cygwin and retain
the more portable alarm()/connect() technique for the other platforms,
and that is what I am considering now.
Regards,
Eric
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
