I had the idea of Partnering different Boinc Projects for Support, Communication and even Advertisement. Two (or more) independent projects (small) could share physical resources for redundancy (similar to printer pooling, two DHCP Servers or linked Proxy servers). Should one projects server be temporarily off-line the Partners server could take over by issuing and receiving Partner Work Units (up to a pre-arranged point) and then their own work units.
That way the clients would be able to get tasks for their elected projects, should the main project server become unavailable. They would also know that should their elected project(s) run out of work units that their partners project would automatically supply them with new units.

Given the competition for client system resources, this would clearly benefit small projects with limited funding and deadlines (to finish Doctorates...).

Ultimately this could evolve to the point where trusted contributors (with permanent IP addresses and descent server hardware) could perform in a distributed support network. There are many crunchers with Permanent IP addresses, good Internet Bandwidth, High end Servers and time on their hands.

---

i like that idea, however, 1 downside is what happened last week, when seti@home went down, it brought boinc mainsite down as well... as they are housed in the same building, and share some equipment.... or something like that..

---

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/

With the suggestion I made there would be at least 2 servers on different sites, for failover. Not 2 projects (well, Seti and the main web site) on the one server!