You mentioned possibly running this in parallel. If you're going to have bugs, it will be there. Especially if you want to have this be cross-platform, abstract out your inter-node communication so that you have a choice for what method (ie MPI, raw sockets, etc) you're using to communicate between computers, and put the network error detection and revival code in there. Design the program as you go with parallel execution in mind to save pain later.
Sadly, this all is not a simple problem.
Slashdot Mirror
I applied for the SOC last summer. I was rejected, but I went ahead and did my proposal anyway.
Now, this summer, I'm interning at Google. So whether or not you can get accepted for SOC doesn't determine whether you can work at Google.
You mentioned possibly running this in parallel. If you're going to have bugs, it will be there. Especially if you want to have this be cross-platform, abstract out your inter-node communication so that you have a choice for what method (ie MPI, raw sockets, etc) you're using to communicate between computers, and put the network error detection and revival code in there. Design the program as you go with parallel execution in mind to save pain later. Sadly, this all is not a simple problem.