You’ve touched on a couple of interesting topics.
“Share nothing” struck me as a “we don’t have a session replication
story” excuse. Which is understandable since Rails is all of 18 mos.
old. The downside of “share nothing” is more round trips to the
Also, I read in AWDWR about the session backing store stuff. I just
accept that sessions will be lost if the container crashes in the J2EE
world (unless I’m doing something like session replication, of course).
The heavy admonition against using an in-memory store for session
backing struck me as odd as a result.
I keep thinking how cool it will be when rails runs on jruby - sure for
access to java objects in the JVM. But then I was trying to think if
there would be any benefit to running rails on JRuby in a J2EE
container, but I couldn’t come up with anything off the top of my head.
Any thoughts? Where would a J2EE container fill in the gaps in the
Rails world? Would having access to JNDI repositories be exciting?
What about JDBC/ActiveRecord stuff? Any thoughts?
Ben M. wrote:
Tom M. wrote:
I can’t think of his name, but I know at least one list reader is
to give you a big “Hallelujah!” on that one!
That would be me… the container junkie.
Actually, I started out arguing for a container because, well, that’s
the way we do it in
the java world. But in the course of that, I came to understand the
benefits of the “share
nothing” approach… I can see why many people like mandating
themselves across the board.
However, I also like having an application context if I need it (I know,
I know… I can
make whatever I want available by DRb… but it’s not the same.) And
ultimately it would
be nice to have the choice. That would be another trump card for Ruby
actually, cuz in the
Java world it’s pretty much servlets or nothing.
Wes, thanks for the tip on Cerise… will keep an eye on that. I wonder
how hard it would
be to get it to run a rails app?