Use COM, either by making it a "script component" or using ActiveState's server maker from their dev kit. Or, use a remote shell (unrelated to Perl). Or, have the script, already running, listen for a signal on a socket or named pipe and GO when the client tells it. | [reply] |
I'd just go with standard TCP/IP (sockets) servers and clients. Simple, portable, well documented and supported.
My second choice should probably be the RCmd service and client from the WinNT resource kit (though I haven't used these with Win2K).
-
tye
(but my friends call me "Tye")
| [reply] |
| [reply] |
You could also use apache and mod_perl or CGI. This will give you a very flexble platform to work from. Of course it'll eat a bit more ram than the other options.
Once apache is running and serving your scripts (or wrappers for your scripts) as CGI, you can trigger them with any http client (such as IE or something whipped up in LWP).
TGI says moo
| [reply] |