dreamhead wrote:
Hi!
JRuby has a wonderful idea about method which is to generate method
class. We all know that it takes some time to do that, so it's good
idea to save the result.
In JRuby, DumpingInvocationCallbackFactory is used for this purpose.
But the code with which save the result is c
Hi!
JRuby has a wonderful idea about method which is to generate method
class. We all know that it takes some time to do that, so it's good
idea to save the result.
In JRuby, DumpingInvocationCallbackFactory is used for this purpose.
But the code with which save the result is commented. I think
Alan McKean wrote:
So far, everything seems to work. But I have some questsions about the
runtime. When Rails is running multiple runtimes, does it maintain a
pool of them or does it instantiate a new runtime every time it needs
one. I currently have only one runtime. It's a singleton and I u
Robert Egglestone wrote:
When using GoldSpike with Rails it uses a pool of runtimes. The
runtime handling
is done outside of JRuby. Loading a new runtime and the Rails classes
is quite
slow, so we've got a custom object pool implementation to manage the
runtime
instances.
When using Webrick o
When using GoldSpike with Rails it uses a pool of runtimes. The runtime
handling
is done outside of JRuby. Loading a new runtime and the Rails classes is quite
slow, so we've got a custom object pool implementation to manage the runtime
instances.
When using Webrick or Mongrel, there would be on
