netErrSocketBusy means the previous activity is still in progress on the socket. A connect takes time to either complete or fail. Different networks may have different completion times.
Are you using the socket in non-blocking mode? If so, this is telling you that your previous connect is not finished. If you want to cancel the connect, either set the socket to blocking and call connect to wait it out, or close the socket to cancel the connect. netErrSocketBusy on a non-blocking connect is a great tool for connecting asynchronously. Initiate the connect, which will return busy, connected or some real error. While not connected or a real error, go do other stuff and then come back and try again. Eventually, you'll connect, get a real error, or you'll decide you're tired of waiting (timeout). On 10/2/06, Troy Lokitz <[EMAIL PROTECTED]> wrote:
Does ANYONE know what netErrSocketBusy means on a netlibsocketconnect call? Why would I get this? -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
-- yisdersomenimororsisasisdenderisorsis? Jeff Loucks -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
