in reply to Re: Re (tilly) 1: distribute render jobs
in thread distribute render jobs

No, just piggyback off of a database. :-)

Seriously, have a relational database with transactions. When new jobs need to be done, add database entries for the needed work. Have a simple client process in a loop. It is connected to the database. At the start of the loop it tries to open a transaction and get work assigned to it. If it can it then does the work (ie one render) and marks it as done. If it cannot it sleeps for a while and tries again.

You can have other processes that add needed renders, check to see whether anything is taking a suspiciously long time, etc.

Replies are listed 'Best First'.
Re: Re (tilly) 3: distribute render jobs
by dystrophy (Monk) on Nov 17, 2000 at 01:02 UTC
    I really like the idea of a relational database. This could make my life easier for the next 2 months! :-)

    Thanks again for your ideas and help.

    -dys

    checkout http://www.dougstruthers.com