🚀 go-pugleaf

"Dennis Jones" <nospam@nospam.com> wrote in message
news:45b9274f@newsgroups.borland.com...

> When I try to establish a connection with a server, IdTCPClient's
Connected
> property returns true almost immediately upon calling the Connect()
method

If Connect() exits without throwing an exception, Connected() is
guaranteed to return true until you perform a read/write operation.
Remote disconects on a blocking socket be only be detected after a
read/write operation has been performed.

> and stays true until the call times out (if the server is
unavailable).

You can't call Connected() while Connect() is still running.  The
state of the connection is not stable until Connect() exits.

> It seems to me that the Connected property should not return true
> until a connection is properly established.

It doesn't.  Part of Connected()'s internal logic is that is reads any
pending data from the socket (to see if the OS reports whether the
socket was disconnected by the server), and then returns whether the
socket is currently allocated.  In the case of Indy 10, Connected()
also returns true if there is unread data in the connection's
InputBuffer.

Besides, you shouldn't be calling Connected() until Connect() exits
anyway.  Why are you doing that?

> How can I determine the *true* state of the client?

Stop calling methods out of order.


Gambit