well. verisign just announced what is basically the idea i have been working on for a while now.
bummer. while verisign's offering does not encompass everything i've been thinking and writing about, there is so much overlap that it's pointless to continue (actually there is one thing that's very distinct, which i'll still file a patent on).
so then: let the job search begin. btw, anyone reading this that is looking to hire some enterprise java (not ejb! for so many reasons) folks in the south bay, check out my resume. please.
grampa hangs on - and more or less, he is himself, although his state of mind reminds me of a story i read once; i'm sure it's familiar, maybe harlan ellison or something - anyway, the protagonist loses his memory each morning, and has to start over (a movie, maybe?). that's what it's like for grampa, but it's sometimes minute by minute that he forgets instead of overnight. physically, he's barely able to feed himself, let alone clean himself or stand up and walk. but, and this is the most important thing, he is comfortable, and he expresses that he is happy that we are around so much ("we" is mainly my mother and myself). several cardiologists told us he would be dead within 3 weeks; we're going on 5 months now. this is a long road that has left me an emotional cripple in some ways.
code? what freaking code? i've let dcserver just sit idle, and while i've been boning up on tech stuff to be ready for interviews, i haven't done anything real in more than a month. time to get back to it. i started implementing (*again*) my multicast-and-rmi failover algorithm, after some design changes this time; constraints are weakened a bit, which i think is fine considering the domain. so, i'll finish my failover thing, add client connection stuff to it (right now it's just the hot and warm servers talking to each other), maybe add a new sourceforge project for it, and then get back on making dcserver an osgi-compliant service platform.