Some people believe mod_rails would be better served by using rack
...
yeah the idea is for this to be merged into rails proper once it is
complete and tested, the core team knows of my work and says it will
make it in once it is done. As far as mod_rails goes... I think they
made a huge mistake by not using rack as their interface, so I'd hope
they will realize this and add rack support. mod_rubinius is all rack
based and will be able to run any ruby framework or simple rack
handlers you can throw at it.
...
-Ezra
http://brainspl.at/articles/2008/04/25/hey-rails-nice-rack
Nirvana would be, seeing as you can limit it to say 4 processes per
rails app.
Say you get 16 simultaneous requests--nirvana would be that they would
all get sent to the same apache threads, so that it didn't unnecessarily
use up apache threads all waiting on rails' existing processes to
finish. Like a flood to a single rails app wouldn't distract from other
traffic.
That would be awesome! I'd be able to sleep at night knowing rails is
not hurting others on my shared host.
-R
If the FrameworkSpawner is running, then spawning time will decrease
significantly. The framework will not have to be loaded at all - only
the application code will have to be loaded.
Is there a way to force a FrameworkSpawner to start when Apache starts?
Would you need one or multiple instances?
Is there a inactivity timeout on the FrameworkSpawner once started?
