"Jamie Dale" <j.dale@turboz.net> wrote in message
news:4522a522@newsgroups.borland.com...
> I know you'd like me to upgrade but V10 seems to be the downfall of Indy
Why do you say that?
> V9 I continue to see bug reports for on the newsgroups.
These are support newsgroups, afterall. Most postings are problem reports,
and even then only by a small group of users who know where to send such
reports. That doesn't mean the version is not usable to the general masses.
A lot of users are using it just fine.
> V8 despite it's age doesn't seem to be raising many issues here apart
> from my lack of knowledge.
And its lack of features.
> Sorry if I sound arrogant with this attitude but after my experience with
> Indy 10 for .NET and the compilation errors I decided to wait until the
> Indy pit crew manage to put together a full proper release which has been
> zipped. Not a live copy which they work on and may not work.
I wouldn't hold my breathe for a full release anytime soon. That is simply
the nature of open source projects. The code is always "live".
> I don't have ReadTimeOut.
Yes, you do.
> Bearing in mind I am still using V8.... I use IdTCPClient1.ReadLn().
> I'm assuming it works the same way as IdTCPServer's
AThread.Connection.ReadLn()
> ?
The TIdPeerThread.Connection property is a TIdTCPConnection descendant.
TIdTCPClient is a TIdTCPConnection descendant. Thus, they sharing the same
ReeadLn() method.
Gambit
