Hi, everybody!
I've started to write a modular user administration
tool sometime ago. During this process, I've also
started two modules facilitating the creation of
such a modular program.
The program modules are realized as Perl classes,
each of them being a child of one of the two
modules I
Randy W. Sims wrote:
Baltasar Cevc wrote:
Hi, everybody!
I've started to write a modular user administration
tool sometime ago. During this process, I've also
started two modules facilitating the creation of
such a modular program.
The program modules are realized as Perl classes,
each of them
Hi everybody,
yesterday, when writing the core of another daemon intended to run
on one of the servers I administer, I caught myself copy-pasting
code from other daemons. Not some lines but more or less the whole
main part.
After a bit of thinking, I realized that there must be a better
solution.
Hi Flavio,
See also: Net::Daemon
Thank you for the pointer - it should appear in that list -
however, at least I have some daemons not having any direct
connections to clients (a daemon that updates the different user
lists from one central data source, a daemon which updates the
iptables
::Daemon or
to downgrade Net::Daemon (which seems more similar to what I
thought about).
Baltasar
Randy W. Sims wrote:
Baltasar Cevc wrote:
One possibility would certainly be to generalize Net::Daemon
to something like a App::Daemon or Proc::Daemon (the latter
exists, but has only a limited
Hi there,
I wrote a little plugin manager module which should be usable for
more or less any kind of application.
The goal was to do provide a standarized interface to create an
application (script/daemon/etc.) with support of plugging in
modules.
The most similar module I know is
A. Pagaltzis wrote:
* Baltasar Cevc [EMAIL PROTECTED] [2005-03-10 13:25]:
use Modularizer;
Well, I can't think of anything really helpful right now, but I
have to register that that name is pretty horrible. It should
definitely be in Module:: and mention Plugin somehow. Maybe
