🚀 go-pugleaf

"Ronny" <potapenko@check.com> wrote in message
news:41d307a3$1@newsgroups.borland.com...

> In the command handler for the LOGIN command,

I would suggest the OnConnect event instead.

> client * newClient = new client(ASender->Thread, login)

Is the client class derived from TObject?  If not, then you need an
OnDisconnect handler in order to free the instance properly.

> This stuff seems to cause some AV when the client disconnect.

You did not show your disconnect code.  My guess is that your client class
is not derived from TObject, and you did not provide an OnDisconnect event
handler, so the TIdPeerThread tried to free the object assigned to the Data
property and thus produced an AV.  The object assigned to the Data property
is owned by the TIdPeerThread.  When the thread is freed, the Data object is
freed as well.  If the object derives from TObject then this works fine. But
if it is not derived from TObject then TIdPeerThread has no way of freeing
it safely so you must free it your manually via the OnDisconnect event.

The alternative is to derive your client class from TIdPeerThread itself,
and set the server's ThreadClass property accordingly.  Then you do not need
to use the Data property at all, and you can cast the Thread property of
each TIdCommand to your derived class directly.


Gambit