This is what we have done for a number of projects on Windows and UNIX.
We haven't found any gotchas with this approach. The only headaches were
related to MS doing things their own special way.
I'll be loading v5.0 this weekend, to make sure there's no problem in that environment.
One piece of advice, make sure you keep track of the last message received
from the notifier server in your daemon/service. If you haven't received one
in some interval (you decide), send a heart beat, if you don't receive it, re-register.
I discovered that the remedy notifier server will drop a client every now and then.
Edward
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
= Elegant Software Producers Tel: (408) 293-5600 =
- 1009 E. Capitol Expwy, Ste 301 Fax: (408) 292-7956 -
= San Jose, CA 95121 E-mail: eebrown@elegantsp.com =
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jarl Groneng wrote:
**
Hi,
Anyone using the notification system to running external processes?
We are using heavily external processes when sending emails. Every times an
external process are started this fires a perlscript(ARSPerl) and/or a C
api. To reduce the load I'm planning to create a notifier client (in Perl or
C), this login and waits for a notify. When a notify is recieved this then
get some information and then send the email, and wait fot the next notify.
--
Jarl Groneng
__
You may also control your subscription options, including UNSUBSCRIBE, at www.ARSLIST.org
Previous Topic
Index