Further thoughts...
I'm sure Remy said a while back in another topic that the OS itself will
time out if a socket doesn't connect.
I think Indys timeout is just a timeout if the server doesn't acknowledge
the connection in a reasonable time - I think if the OS itself accepts the
connection the timeout doesn't work - Only if the server doesn't respond...
I'm probably wrong but thats a vague memory...
"Jamie Dale" <jamie.dale@yahoo.com> wrote in message
news:487f5119$2@newsgroups.borland.com...
>
> "Man T" <alanpltse_NOSPAM@yahoo.com.au> wrote in message
> news:487e97f5$1@newsgroups.borland.com...
>> "Jamie Dale" <jamie.dale@yahoo.com> wrote in message
>
>>>> inherited;
>>>
>>> I'm reckoning it might be something to do with the above...
>>
>> So do I use 0 or leave the parameter blank to set the timeout as
>> infinity?
>> ie
>> IdSMTP.Connect(0)
>> or
>> IdSMTP.Connect()?
>
> I'm reckoning you would use a 0 - as in 0 for no timeout. I couldn't
> promise though as its just a guess. I'm not that knowledgable with how
> indys internals work - I just noticed the inherited bit which would
> explain what you were looking for.
>
> I'm sure Remy will be able to give you a better idea.
