Things I did instead of doing the jsync conduit:
- Made a big sticker for my laptop that says "MY OTHER COMPUTER IS A BEOWULF CLUSTER". That makes up for how.. uh, speed challenged it is.
- Read about
wild monkey sex bonobo society. Bonobos are neat.
- Realized that the pilot-link conduit isn't quite finished yet, and worked on that.
The one last problem with the pilot-link conduit is that if a network request takes too long, the HotSync will time out because no communication with the pilot is going on. Enter pthreads. I've never used pthreads before, but it seemed to be easier than I thought. Still, if you've ever done any threads programming, I'd appreciate a "*nod* you did it the right way".
When the Conduit object is created, it creates a mutex and launches a new thread. The mutex is locked whenever the main thread is communicating with the pilot. During network transactions, it's unlocked. The pinging thread looks like this:
It actually seems to work. I firewalled out livejournal.com and ran ljsync. Every HTTP request timed out, but the HotSync process kept running til the end.