🚀 go-pugleaf

Ahh.  Something (__classid) I've never used before.  Very cool. 
Works like a charm.  Thank you!

I've decided to use a descendant thread class instead of .Data
since it seems that I have finer control over when and how user
objects get created and destroyed.  One of the data members is
a pointer to a dynamically created structure.  The short of
all this is that all of your suggestions have led me to using
Indy in the intended way instead of the old WinShoes way.  The
application is much more responsive to socket connects and disconnects.

Paul Mac - Completely Satisfied Indy/Winshoes User Since 1999 - :-)

"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>
>"Paul Machiaverna" <paul.machiaverna@i-stat.com> wrote in message
>news:41b07de3$1@newsgroups.borland.com...
>
>> Okay, that answers how to attach user data to a thread.  Now, I
>> just have to figure out the syntax for assigning a descendant class
>> of TIdPeerThread to TIdTCPServer::ThreadClass!  :-o
>
>Use the classid keyword:
>
>    IdTCPServer1->ThreadClass = __classid(TMyCustomPeerThread);
>
>
>Gambit