in reply to SOAP::Lite and Win32::Daemon

I'm currently working on similar code.. Instead of using Win32::Daemon, I just have a script that runs in a while loop. It's not the cleanest thing in the world, but I can have a "daemon" running and processing messages as necessary. I know that SOAP::Lite can be run as a daemon.. 
my $daemon = SOAP::Transport::HTTP::Daemon
  -> new (LocalAddr => '207.000.000.000', LocalPort => 80)
  -> dispatch_to('_Whatever')

[download]
That processes under sigint properly. It's what I'm using. The package it dispatches to is internal. All it has is two subroutines. One for stuffing messages into a table. One for picking them out of an outgoing messages table. The "deamon" mentioned above does the work of running under the while loop and grabbing the messages out of the db. It's not much, but it's just my two cents. I hope I could offer at least a view of what somebody else is trying out.


One4k4 - perlmonks@poorheart.com (www.poorheart.com)

Replies are listed 'Best First'.
Re: Re: SOAP::Lite and Win32::Daemon
by bobtfish (Scribe) on Feb 04, 2004 at 18:04 UTC
    The problem with that is that I need this script to start at boot time and run without user intervention / ability for user to kill it off..
[reply]
      If you're running at least Windows 2000 Server, just go into scheduled tasks, and create one for this process. Set its run time to "At system startup" and don't allow it to interact with the console. Users won't see it unless they look at the process list, and it will run even when no one is logged in. That's how we run our Wiki script. Much easier than a service wrapper if you just need to get it running quickly.

      Of course a service is the right way to go if you want remote start/stop and stuff.

      --
      Spring: Forces, Coiled Again!
[reply]

In Section Seekers of Perl Wisdom