in reply to Should this be a Windows Service ?
The operator turns on the process hardware, starts the daemon, opens a web browser, works for 8 hours, then turns everything off. Normally, the platform would be a dedicated single-user PC, but out in the real world, it could be run on a laptop or a multi-user PC. So, to make it resilient against an operator inadvertently logging out while the process runs unattended for an hour, I think the daemon should continue to run with no one logged in. So I think I need a service.
The browser (either the local one or another one on a LAN) can not start or stop the daemon.
The system requires Apache to be running, and Apache has a system tray starter/stopper. Part of the startup procedure would be to click the Apache icon and ensure that Apache is running. Thus my idea for a system tray icon for starting and stopping my daemon – the operator goes to the same place to perform both functions – and my icon should act similar to Apache’s. So I’d like to keep the icon.
OK, so two distinct programs. Got some questions.
Service – the service is supposed to be able to pause and continue, but that makes no sense in my application. How do I tell Win32::Daemon “can’t pause”?
Icon – (1) the Apache icon appears whenever a user logs on, and it can also be added/removed from the Start Menu. How do I get mine to appear whenever a user logs on? (2) The Apache icon knows the status of the Apache service. How does it do that?
Dave
|
|---|