Hi everyone

A thought went through my mind this morning and I've been chewing on it a
bit during the day, and will continue to do so over the next couple of days.
I thought it would be wise to dump some random information here (nothing
solid) to see if it sparks a healthy debate...

DaemonKit Stackable Environments

Rough Cut: DaemonKit can benefit hugely from a stackable environment, like
rack, but the stack gets "compiled" only once. The stack is responsible for
setting up an environment for the daemonized code to run in.

Parts affected:

* Dependency loading (can greatly simplify this)
* Boot (pre-daemonize)
* Run (post-daemonize)

Different stacks? Or one stack with stack entries being called at specific
times if needed... Probably single stack, with stack members possibly
exposing several different hooks that can be called at various times during
the daemonization process.

Benefits

* Much easier to add/remove daemon-kit features as you need them
* Easier to hook in customizations
* Easier to extend (and easier to compact)
* Familiar concept (rack), slightly different implementation

Pitfalls

* Deep rewrite of dk
* All existing daemons would have to change
* Familiar concept (rack), slightly different implementation (yes, repeated
on purpose)

Everything is conceptual at the moment, and subject to change or complete
nullification if I sober up to something better... If this sounds like a
good idea, especially with a experimental branch evolving, I'll announce
more to the group.

Anycase, thanks for listening and looking forward to any questions and
critique...

Ciao !

--
Kenneth Kalmer
kenneth.kal...@gmail.com
http://opensourcery.co.za
@kennethkalmer