note jfroebe <p>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.</p> <p>One idea that looks like it might have hope is:</p> <ul> <li>A message bus (possibly <a href="http://search.cpan.org/~dsnopek/POE-Component-MessageQueue">POE::Component::MessageQueue</a>) that will allow job queuing, job statuses, etc to be communicated to the N nodes</li> <li>Static job list, statuses, etc via a replicated db. Possibly using <a href="http://search.cpan.org/~dgl/Net-CouchDb">Net::CouchDB</a> - this would also be used as the backend to provide statuses to a front end of some sort (web or similar).</li> <li>Configuration of the peer job 'servers' via a simple ini file (<a href="http://search.cpan.org/~sherzodr/Config-Simple/Simple.pm">Config::Simple</a>)</li> </ul> <p>Thoughts on this hair brained idea?</p> <!-- Node text goes above. Div tags should contain sig only --> <div class="pmsig"><div class="pmsig-304796"> <p>Jason L. Froebe</p> <p><a href="http://jfroebe.livejournal.com">Blog</a>, <a href="http://www.froebe.net/blog">Tech Blog</a></p> </div></div> 814657 814662