Fabio Kung wrote: > > On Fri, May 2, 2008 at 6:00 AM, Christian Seiler <[EMAIL PROTECTED]> > wrote: > >> Wouldn't that mean that JRuby instances can't easily share objects any >> longer? I'm thinking of things like Rails instances sharing an EHCache or >> Spring application contexts. This is really a sweet spot of JRuby IMO >> that >> you can efficiently share data inside a single JVM without the need to do >> any inter process communication (as long as you don't need to scale out). > > > Actually they can, as long as shared object classes are loaded by a common > parent classloader. It would work if the JRuby instances have a single > common classloader (application classloader, servlet context classloader, > ...) and shared object classes were loaded by this parent classloader. >
Yes, but right now I happily and simply instantiate this shared stuff in Rails plugins. I think I wouldn't like to mess around with classloaders. It would be really an annoyance to me. -- View this message in context: http://www.nabble.com/More-ideas-for-perf%2C-integration-tp16997874p17024444.html Sent from the JRuby - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
