Basierend auf der Arbeit von Josh Peek, Mitglied im Rails-Core-Team, während des aktuellen Google Summer of Code, soll Rails 2.2 jetzt offiziell Thread Safe werden.

Was diese Thread Safety nun aber genau bedeutet und welche Auswirkungen sie auf die Ruby- und JRuby-Gemeinde haben wird, erklärt Charles Nutter, Core-Developer im JRuby-Projekt, jetzt in seinem Blog.

And it doesn't end at resource utilization in JRuby's case. With a single Rails instance, JRuby will be able to "warm up" much more quickly, since code we compile and optimize at runtime will immediately be applicable to all incoming requests. The "throttling" we've had to do for some optimizations (to reduce overall memory consumption) may no longer even be needed. Existing JDBC connection pooling support will be more reliable and more efficient, even allowing connection sharing from application to application as well as across instances. And it will put Rails on JRuby on par with other frameworks that have always been (probably) thread-safe like Merb, Groovy on Grails, and all the Java-based frameworks. Charles Nutter, 2008