🚀 go-pugleaf

"Fred W." <fwestphal@tomtec.com> wrote in message
news:40E01817.DAEBAD67@tomtec.com...

> I am developing a service which needs to communicate
> with a user application using inter-process communications.

You can't use window messages for that anyway.  Services run under a
completely different desktop and workstation to begin with, thus a service
could not find, let alone send messages to, a window on a different desktop,
and vice versa.  For IPC with a service, you should use ActiveX/COM, RPC,
Named Pipes, or TCP sockets instead.

> One thought is too somehow have the service spawn a
> process in the active session. I could than preserve the
> Windows Messaging protocol I have already developed.

The spawned process would still be running in a different
desktop/workstation than the service, thus window messages still unusable.

> The other obvious thought is too rewrite my code using a
> better IPC method that can more easily handle the
> multi-session scenario.

Yes.


Gambit