It's Like Déjà Vu All Over Again
"You could probably waste an entire day on the preceding links alone. But why take chances? We also give you Paul Snively..." — John Wiseman, lemonodor
Hey, check it! Jim Roepcke, one of Frontier's grand old men who's developed some amazing—and amazingly useful—stuff for various versions of Frontier over the years, was kind enough to include me in his list of Frontier old-schoolers who've signed up for Radio.
I have to say it's taken me some time to immerse myself in the new Radio universe, but 8.0 is making it a lot more transparent than 7.0 did. I'm also fortunate enough to have hosting for my biggest-itch project at the moment on one of UserLand's servers, over at <http://seppuku.editthispage.com>, in addition to this more general weblog. So it's time for me to learn how to take advantage of the tools more effectively, and hopefully even contribute back more meaningfully. I'm not sure yet what form that might take, and I'm not going to rush myself. But Radio 8 has already made me feel more connected with the community than I ever have before. Regardless of how it flows, it'll be great to see how that connection evolves. I'm definitely buying another license for my Windows machine at work, and I'll be recommending it to friends, no doubt.
1:50:59 PM
For those who don't know, Resin is a top-flight Java Servlet/JSP engine. Resin-CMP is a top-flight EJB Container-Managed Persistence engine. And although no link has shown up on freshmeat for it yet, Resin-EJB is a top-flight full-on EJB 2.0 implementation. With Resin-EJB's Message-Driven Beans and a good JMS like SwiftMQ you have an excellent platform for Enterprise Application Integration and constructing web services via Resin's Burlap protocol, which is XML over HTTP like XML-RPC or SOAP, but is more expressive than XML-RPC and less complex than SOAP.
1:44:29 PM
We present an implementation of the Train Algorithm, an incremental collection scheme for reclamation of mature garbage in generation-based memory management systems. To the best of our knowledge, this is the first Train Algorithm implementation ever. Using the algorithm, the traditional mark-sweep garbage collector employed by the Mjølner run-time system for the object-oriented BETA programming language was replaced by a non-disruptive one, with only negligible time and storage overheads.