🚀 go-pugleaf

"Remy Lebeau (TeamB)" <gambit47@yahoo.com> wrote in message
news:3f47d014@newsgroups.borland.com...
>
> "BlackFrancis" <areyouabot@toobad.com> wrote in message
> news:3f46e02e$1@newsgroups.borland.com...
>
> > I have been able to send messages (using SendMessage) and
> > recieve them by overriding WndProc.  My problem is now that I
> > want to send a message to a TService.
>
> Services do not accept messages like you are thinking.
>
> > TServices aren't allowed to have Controls
>
> That's not entirely accurate, but it takes a lot of work to set it up
> correctly, so it is best to not put controls in services directly.
>
> > Is there any way around this, or will I have to try
> > an alternative messaging methodology?
>
> You will have to set up and establish a different kind of IPC
(inter-process
> communication) connection to the service.  Depending on the nature of your
> messages, if they do not have any parameters, then you can use
> ControlService() to send custom control codes to the service.  TService
has
> a protected DoCustomControl() method that you can override for processing
> them.  Otherwise, you will need to use named pipes, TCP sockets, RPC
(Remote
> Procedure Call), COM, etc instead.
>
>
> Gambit
>
>
>

Thanks for that.  I have now been able to write ControlService code that
makes a call to the Service, using an SCManager handle.  What I don't have
is the message handling routines in my TService.
Could you briefly explain (possibly with sample code) how this is done?
Thanks again