On 2006-12-19, G.H. <[EMAIL PROTECTED]> wrote:
> Thanks for replying Tuomo. I'll like to hear more about your ideas on
> daemon modules, can you give us a little more illustration on that ways?
> That could be a very big step forward for the mighty Ion.
It's not about daemon modules. All the existing statusd scripts should
continue working. But I've been thinking of separating ion-statusd into
a project of its own, and improving it.
* It should listen to a unix socket instead of Ion starting it with
a one-way pipe, allowing other programs to access the status
information as well, and the statusd being more easily restarted,
and even started completely separately from Ion, replaced, or whatever.
* It should support loading scripts/plugins by instructions through
the socket.
* Maybe it should also work as a "status distribution node", so that
you can run other status daemons (possibly written in other languages)
that 'inform' ion-statusd of their status through the socket, and
ion-statusd then distributes this information to listeners.
(Infact, mod_statusbar could inform statusd/other programs of Ion's
status.)
* (Format of the socket protocol can be similar to the present:
load: script
param1: val1
param2: val2
.
I'm unlikely to waste my time on this as it's not that essential,
but it would be nice if someone else got around to doing it...
--
Tuomo
