> Excuse me for my ignorance but I am not sure if ActiveRecordStore for
> session would be faster than file system session store?
It's most likely not.
And, to speak with someone elses words: that's not a problem until it's
Once the AR session store proves to be a bottleneck, you can always
replace it with a faster, still MySQL-based solution (afair the Rails
performance blog had a post about this some time ago). And if that still
doesn't work out, you can go back to solve the problem by choosing
another session store, or even by implementing your own
> BTW its really surprising that there is no rails setup for a transparent
> failover, the idea of which can be sold to large corporations like mine.
> I think this is a common requirement nowadays when most web applications
> require 99.95% uptime.
> I am not so highly qualified to take on such a
> task, but unless issues like this are tackled RoR adoption rate in
> corporations will be extrememly low at best.
What you want to do isn't a function of the application server,
whether it's rails, mod perl, jboss, whatever.. Load balancing and
failover is handled by other layers. Just because you aren't familiar
with the different tools available to you dont' assume they don't
exist. I already pointed three that would probably do the job.
Squid, Pound, or something like a ServerIron, and there are more if
you look around.
Pen can do session aware load balancing, too. In fact it's
not really session-aware, it simply assigns same clients (IP-based, I
suppose), the same Mongrel instance with each request.
Don't know about Windows support, though.