>> Sorry I wasn't talking of the actual threads that the indy server
>> automatically deals with - I was talking of the AThreads for the
>> actual connections of each user.
>
> They are the same thing. The AThread parameter of TIdTCPServer's event
> handler is the thread that the server created to manage the connection for
> a
> client.
Ok lol, well either way it using an array still allows me to keep all the
users data and a pointer to the AThread. That means I can find their
connection and write to it fairly easily. Imagine if I assigned their info
to the Thread data - I'd need blank threads for the users that wern't even
logged on etc. Using an array makes it a lot easier from my POV.
Of course, if you have some tips?...
Also, seeing as each thread has access to the array, how can I stop it being
damaged/corrupted?
Can you provide any sample codes?
