🚀 go-pugleaf

"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>
>"Peter" <piotrtrzeciak@yahoo.com> wrote in message 
>news:479e2c75$1@newsgroups.borland.com...
>
>> The main server (TIdTCPServer) component is part of the TService
>> application, and in it's main Execute thread, it is started like this:
><snip>
>
>Get rid of that OnExecute handler altogether.  TService already runs such a 
>loop internally for you when no OnExecute handler is assigned.  Instead, 
>activate the server in the OnStart event, and deactivate it in the service's 
>OnStop/Shutdown events, ie:
>
>    void __fastcall TMyService::ServiceStart(TObject *Sender, bool &Started)
>    {
>        iln_rcv_socket->Active = true;
>        Started = true;
>    }
>
>    void __fastcall TMyService::ServiceStop(TObject *Sender, bool &Stopped)
>    {
>        ServiceShutdown(Sender);
>        Stopped = true;
>    }
>
>    void __fastcall TMyService::ServiceShutdown(TObject *Sender)
>    {
>        iln_rcv_socket->Active = false;
>    }
>
>
>> This seems to be working ok, however, it appears that I can only
>> get the first connection to come in ok, and the rest after that fail.
>
>TIdTCPServer works fine in a service environment.  If you are having 
>problems with connections, then your TIdTCPServer event handler code is 
>likely buggy to begin with.
>
>> I also added TIdAntiFreeze component to the TService application
>
>TIdAntiFreeze is useless in a service.  It operates only in the context of 
>the main thread, and acts as a no-op in worker threads.  TService does not 
>run in the main thread.
>
>> Also, I assume that all storage in OnExecute handler of the TIdTCPServer
>> is local to the each thread.
>
>What "storage" are you referring to exactly?
>
>
>Gambit 
>
>

Thanks!!! This is great! It's the lack of documentation that's driving me nuts :-) but I'm chugging along. I have a few other "variables" in the picture (like a third-party imaging libs), so anything is possible as far as "bugs" go.
I have lots of info to go on for now. Thanks again!