🚀 go-pugleaf

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

> If the state is not known, then why does 'Connected' change from
false
> to true while it is trying to connect?

I already answered that earlier - the documentation explains exactly
what causes Connected() to return True.

> I fail to see anything that even remotely suggests that it returns
> true when it is in the process of establishing a connection.

Then you did not read it very carefully:

    TIdTCPConection.Connected()

    "Connected returns True when the connection contains a valid
IOHandler with a bound socket handle for the connection, and the
connection has not been closed unexpectedly."

In this case, "bound socket handle" does not mean "connected socket".
It means "allocated socket", as returned by the API socket() function.
TIdTPConnection.Connected() internally calls TIdIOHandler.Connected(),
which is a virtual method that involves all three of the following
methods (in this order):

    TIdIOHandlerStack.Connected()

        "Connected() calls the inherited method to retrieve the return
value for the function. The return value for the function is True when
the InputBuffer contains exisiting data, or when ClosedGracefully is
False and the InputBuffer is assigned."

    TIdIOHandlerSocket.Connected()

        "The return value for the method is determined by the values
provided by BindingAllocated() and the inherited Connected() method."

    TIdIOHandler.Connected():

        "The return value for the function is True when the
InputBuffer contains exisiting data, or when ClosedGracefully is False
and the InputBuffer is assigned."

Nothing in that says the connection has to actually be established.
Only that the socket has to be allocated and not considered
disconnected.


Gambit