>I have an application that uses a TTnCnx object to repetitively retrieve
>data from a remote device. The application keeps a TTnCnx object and
>alternately Connects and Closes. I am having an occasional problem with
>the connection getting latched up, that is, it doesn’t seem to close
>properly and since the receiving device only supports one session,
>communication is stopped.

>Is there a problem with calling Connect again too soon after a Close? Is
>there some status I should be monitoring?

Maybe the device doesn't like a reconnect too fast ?

I don't know how you coded the application. If you call Connect from close
event handler, try to pass by an intermediate custom message to let the
component stop closing completely before doing anything else.
Author of ICS (Internet Component Suite, freeware)
Author of MidWare (Multi-tier framework, freeware)

To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to