moxi as an NT service, potentially through port_adaptor

We need a 'standalone' moxi to run as an NT service.

One approach is to extend port_adaptor.exe on windows to optionally be registerable and runnable as an NT service. This enhanced port_adaptor should then generically be able to spawn any console-less command-line program (like moxi.exe).

The resulting enhanced port_adaptor needs to be...

• an NT service

• configurable
  • such as by storing configuration in the windows registry or well-known file location that the NT service can access
  • the port_adaptor then can spawn the child program from the right directory, path, environment vars, and with the right command-line

• handle output/logging/errors
  • such as by forwarding child stdout/stderr output to the windows Event Log
  • raising errors to the user's attention (such as port number taken) in a windows-specific way is important

See: http://en.wikipedia.org/wiki/Service_wrapper

Steve

----Original Message----
From: Steve Yen
Sent: Thursday, August 12, 2010 10:54 PM
To: Sharon Barr; Trond Norbye
Subject: RE: Didn't we port the stand alone moxi to windows?

Trond did port moxi to win32. But, there's no separate installshield project for a standalone moxi setup.exe, and no work on that has been started. It should be pretty straightforward for Dmitry to extend wallace to provide that.

Currently, on windows, moxi is comprised of an executable (moxi.exe) plus 2 required DLL's (pthreadGC2.dll and libcurl-4.dll). Those DLL's can probably be compiled into a moxi.exe statically, to result in a single *.exe, too, if we want that.

To 'productize' moxi to be more standalone-friendly for windows, we might need to make it into an NT service, but that can probably be later.

Steve