As I understand NetLibSelect, The situation... If a socket is set to non-blocking, a connection is requested, and NetLibSelect is called to check for the writefds to signal set, according to unix documentation this is to mean the connection is ready for sending data. Under POSE this works. Under Handspring I get a signal before the socket is actually ready - anotherwords, when I do a write to the socket I get an error that the socket is not connected. A bug I presume in the OS as this is straight forward stuff. Any ideas? Please don't suggest to block since the purpose of non-blocking is to give the user a chance to cancel the connection request if the connection were to block for some lengthy time. Joel -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
