Charles Oliver Nutter-2 wrote: > > - Classloader-based runtime separation; instantiating a JRuby instance > instantiates a new classloader and all of JRuby runs under that. This > would isolate JRuby instances and allow access to the runtime through > getClass().getClassLoader().getRuntime() always rather than having to > have a Ruby metaclass around. This in turn would make it possible to do > things like normal Java serialization, instantiable Ruby types without a > runtime passed in, and more. We need to revisit this and try to make it > happen. >
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). Christian -- View this message in context: http://www.nabble.com/More-ideas-for-perf%2C-integration-tp16997874p17009979.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
