Re: [Clockwork-developers] Implementation of a decentralized schedule

[Joel L. <jo...@lo...>]

I don't know about everyone else, but I'm leaning toward a centralized
schedule myself. The decentralized plan has some great benefits, but it
seems like it would be a lot more complicated. While this would allow us
to learn some new stuff like multicast IP while building it, we're trying
to build a product where reliability is essential, and something that's
less complicated is likely to be more reliable.

My other reason for choosing the centralized design is that we all
understand very well how AutoSys, a centralized scheduler, works. We know
the good things about it, and we could improve on the bad things. If we
choose decentralized, we have to start from scratch. 

Does anyone else have an opinion on this now that we've laid some pros and
cons of each approach on the table? We've been at this fork in the road
for a while, and I'm anxious to make a decision one way or the other and
move on with the project.

If you have any thoughts not covered in Brian's compilation, now is the
time to speak up.

-- 
Joel