[
CIO Today noticed microrebooting research paper.]1 While I agree that the paper is very interesting, I think there are some holes in it that were not explored (or at least not explained).
Specifically:
Early in the article, memory leak and resource leaks are named as the problems solved by rebooting. From what I can see, microrebooting will only solve the issues where those resources/objects are held by instances that are cleared on microreboot.
Jeff Mesnil is a developer who had to play ‘support’ for a bit. Specifically, he had to read logs produced by others. He immediately discovers a lot of lessons that are not obvious when you only read your own code.
To his list I want to add a couple of things from my own support experience:
Make sure you have some way to identify which log entries belong together. Use TransactionId if you have one, thread name if you don’t.
A very strong (and quite dark) futuristic look at personalised news and media consolidation (8 minutes). Via Doc Searls. Really worth watching for anybody in the blogosphere.
The idea as such has been covered in Science Fiction before, but the anonymous author of this piece has used the real names and very realistic sounding dates.
After watching the piece come back here and think about this. If EPIC is coming, do you want to be its editor?
I wrote about my impressions from Bloggercon’s Overload session before. Now, Tantek (who works for Technorati) details specific technologiesthat could help to implement the wish list items mentioned.
BlogicBlogger Over and Out
Rich Salz writes about major problem with WSDL 2.I really hope it gets fixed before BEA decides to implement it. Otherwise, it will be completely unsupportable.
We already have problems with handling the customers bitten by vague specs, but this looks nightmarish.
BlogicBlogger Over and Out