thanks! :) Looks like that might help for part of it but... the more I think about this the more I want the p2p job scheduler.
One idea that looks like it might have hope is:
- A message bus (possibly POE::Component::MessageQueue) that will allow job queuing, job statuses, etc to be communicated to the N nodes
- Static job list, statuses, etc via a replicated db. Possibly using Net::CouchDB - this would also be used as the backend to provide statuses to a front end of some sort (web or similar).
- Configuration of the peer job 'servers' via a simple ini file (Config::Simple)
Thoughts on this hair brained idea?