locked
Callback not happening after connect() RRS feed

  • Question

  • All...  My apologies if this is the wrong forum - couldn't find one better suited for the question...

    We have a socket application that listens on one port while trying to make a connection to another application.

    Every 10 seconds the app makes a call to connect(), which yields WSAWOULDBLOCK.  Then the callback hits with FD_CONNECT and WSACONNREFUSED.  This is good and works great.

    Some time later our listen socket gets a connection and we start exchanging data.  Once this connection is established and that 10 second loop hits, things don't work anymore.  We still call connect() and it still yields WSAWOULDBLOCK, but the callback never hits.

    FWIW, this is all on the same machine / localhost in a VS2008 dev environment.

    Any thoughts?  

    Many thanks.  -- Curt
    Thursday, September 17, 2009 10:11 AM

All replies

  • Did you reset your FD_CONNECT. After you receive an FD_CONNECT message you have to reset by calling WSAAsyncSelect with FD_CONNECT to re-arm it.
    And without code it's pretty hard to determine where you're going wrong.

    Saturday, September 19, 2009 4:11 PM