Re: Potential issue in TIdSocketHandle.Readable (Indy 9)

Giganews Newsgroups
Subject: Re: Potential issue in TIdSocketHandle.Readable (Indy 9)
Posted by:  Remy Lebeau (TeamB) (gambit47.no.spam@no.spam.yahoo.com)
Date: Mon, 26 Apr 2004

"Ron" <ron@nospam.simdata.com.au> wrote in message
news:B4A91CD7E09AE240ron@nospam.simdata.com.au...

> TIdSocketHandle.Readable calls itself n-times where
> n =  ReadTimeout / AntiFreeze.IdleTimeout.  If you have
> a large ReadTimeout and a small AntiFreeze.IdleTimeout,
> n can be quite large and take up a fair bit of stack space.

I have changed Readable() in the live version of Indy to remove the
recursion.

Gambit

Replies

None

In response to

Potential issue in TIdSocketHandle.Readable (Indy 9) posted by Ron on Mon, 26 Apr 2004