in reply to Re: Unusual(?) server
in thread Unusual(?) server

As i said early there are situations when server must be able instantly send new state to the client, not waiting for the next connection round. That why i have to to establish connection on server demand or use existing (not closing).

Yes,in general it's a monitor, but with the abitilty to send commands to clients on (user) demand.

Replies are listed 'Best First'.
Re^3: Unusual(?) server
by Aristotle (Chancellor) on Nov 18, 2002 at 09:12 UTC

    All of the monitoring tools I mentioned have the ability to react to defined conditions by executing configured commands. You could f.ex launch a script that invokes a command on the slave using SSH.

    mon might be interesting as it's written in Perl itself.

    The other option might be to write just the part that sends commands to clients but use a monitoring package to do the regular tasks. As the control script runs on the same machine as the monitor, it could peek at the monitor's data and occasionally initiate actions on its own.

    Makeshifts last the longest.

[reply]
      Ok, thanks for links. I'll dig it.
[reply]
      I friend of mine was developing Thoth which again is mainly written in Perl.

      This is extendable and my meet some of your requirements or just give you ideas.

      Hope this helps
      UnderMine

[reply]

In Section Seekers of Perl Wisdom