Hi,

I have a problem with TWSocket.State staying as wsConnecting after I try 
and connect.

I am using a thread to execute an SQL query. For each result from this 
query, I connect to a remote server using the TWSocket, and send some 
data. That's the plan.

In the Thread.Execute procedure, I have created the TWSocket, then I run 
through a state machine to query the database, make the connection etc.

Does anyone know why .State would stay at wsConnecting?

I can connect to the server manually using telnet, and I don't have any 
problems providing additional info. Just didn't want to overload the 
email at this point.

Thanks,

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

Reply via email to