Chaotic Java has an outstanding review of the JVM garbage collectors in two parts. The first is an introduction to mark and sweep garbage collections, and the second is a quick, mostly understandable, review of concurrent garbage collection.
In my experience in working with .Net and Java, I have found that most developers have little-to-no knowledge of the theories behind garbage collection and reference strength. I fear for the future of development if more developers don't understand the tools of their trade in greater detail. Who knows what products they might be working on, or how acceptable a restart every four minutes will be.
Software development, Programming languages, Virtual Machines, Virtualization, and Systems Architecture.
Wednesday, January 9, 2008
Monday, January 7, 2008
Coconut AIO collects dust.
Coconut AIO is part of the Coconut project at Codehaus. The focus of the coconut project is highly concurrent internet services. This includes things like caching, multi-threaded IO, etc. Sadly, the AIO component of Coconut is no longer developed, and is considered discontinued. Even the Coconut website no longer references the Coconut AIO package.
One of the things I liked about Coconut AIO was that it was based around java.util.concurrent.Future objects. This provided more accessibility to junior developers since the whole model behind selector threads, content filters, and registering socket interests can be rather daunting.
Maybe the Coconut group will revisit the AIO package after they finish work on their caching services.
One of the things I liked about Coconut AIO was that it was based around java.util.concurrent.Future objects. This provided more accessibility to junior developers since the whole model behind selector threads, content filters, and registering socket interests can be rather daunting.
Maybe the Coconut group will revisit the AIO package after they finish work on their caching services.
Subscribe to:
Posts (Atom)