🚀 go-pugleaf

I would have like to have all my processing code in another class. This 
class will takeover the client communication since it is not really the 
best place to take care of that in the event of TIdTCPServer OnExecute 
Event. By processing everything in the OnExecute Method, it will not be 
good programming practice I beleive. I think the way the Java class 
handles the client connexion is a good way of OO programming.

thanks for the answer

Simon


Remy Lebeau (TeamB) wrote:
> "Simon Guertin" <sguertin_AT@trellianetworks.com> wrote in message
> news:427a2a63$1@newsgroups.borland.com...
> 
> 
>>Hi, I am a long time Java user, so I think in Java a little bit. I
>>need to create a TCP server and I would like to know if using
>>the TIdTCPServer will be good for me or if I should implement
>>a server that looks like this (at the bottom of the email):
> 
> 
> TIdTCPServer already does exactly the same thing that your Java code is
> doing.  When activated, it runs a continous loop that accepts new client
> connections and spawns a thread for each one.
> 
> 
>>my question is, : I need to know where to put all my processing
>>of the connection.. other than in the TCPServerExecute() method
>>of the IndyServer.
> 
> 
> The OnExecute event *is* where you are supposed to place your processing
> code.
> 
> 
>>Should I re-write my own server..can I change the way the threads
>>are started?
> 
> 
> Why?  Do you have a problem with the way they are currently handled?
> 
> 
> Gambit
> 
>