>IMNSHO it might be easier in the long run to work with message
>handlers instead of events. Map the necessary signals to messages
>in the WM_APP space and broadcast them (blocking: sendmessage,
>nonblocking: postmessage) with the signal in LPARAM and the pid in
>WPARAM, and the 'signalee' takes action following a switch. This
>will minimize the win32 API code except for implementing the callback
>into each backend.
I'd say avoid this if you can.. shared memory and events is cleaner in
that messages are more for GUI apps than for services.. otherwise
you're going to have a window handle and a message pump around just
for this.
Also, there's no security on an HWND, so unless you're going to verify
the permissions some other way you'd lose the security you have
available
to protect you from any process being able to send you signals. This is
the basis for the Shatter attacks on win32.
--
Steve Tibbett
stibbett@zim.biz