I recently moved to Rails 2.0 on one of my projects, and was surprised
and interested to find out that the new session store is client
I'm skeptical about DHH's claim that it will be "zero maintenance."
I have definitely run into bugs/mistakes that I've introduced into my
app. where some piece of pre-existing session data causes an
unwanted/unintended effect after a change. Usually, these issues
resolve themselves, but in some infrequent cases, the easiest method of
fixing it is to shut down the app., clear out some session data, and
restart, ensuring that no problematic "old" session data is present.
Obviously, this kind of recovery won't be very easy if the session data
I have a few questions:
1) Has anyone considered this as an issue with the client - side session
2) Has anyone created a special action that might force the cleanup of a
session, in order to handle cases where cleaning the session might be
3) Also, it just occurred to me that I don't quite understand the claim
that this method is "a lot faster than traditional session stores."
So, now, instead of storing the session data on the same server and
retrieving it over a high-speed network, the session data gets
transmitted on each request/response as a cookie? How is that faster?
Any thoughtful responses are appreciated.