Random_Walk has asked for the wisdom of the Perl Monks concerning the following question:
Greetings honoured monks
I have a client daemon that will be distributed to a (reasonably large) number of machines on our internal network. I need a way to remotely interogate the client for its logfiles, current version etc (this requirement is likely to expand to other methods too). I also need to be able to send it updated config files and updates to the code base. It has to be multi-platform (aix, linux, win32).
I have a client daemon that will be distributed to a (reasonably large) number of machines on our internal network. I need a way to remotely interogate the client for its logfiles, current version etc (this requirement is likely to expand to other methods too). I also need to be able to send it updated config files and updates to the code base. It has to be multi-platform (aix, linux, win32).
I am thinking of a simple server listening on the client and passing requests recieved to subs. Where it need to download stuff I will have it connect to a hardcoded server name to look for and grab a new version (we have control of the DNS).
- Does my approach sound sane
- a maze of twisty server modules ....
- SOAP::Lite
- Net::Server
- Net::EasyTCP
- Net::Server::NonBlocking
- NetServer::Generic
Many thanks for your time and experience,
R.
Pereant, qui ante nos nostra dixerunt!
Back to
Seekers of Perl Wisdom