Sessions

Rails
1

hi all,

in my application, i have login form. while login into the application
iam maintaning the details in session. i want to remove the stale
sessions and while removing the stale sessions i want to perform some
operattions on database . how to do this.

Regards,
Rajkumar

2

On 27 Apr 2010, at 17:44, Andy J. wrote:

The other way is to have a version field checked/set in a filter in
your application and empty any incoming session requests if they
don’t have the right version. It won’t delete them all immediately,
but at the time they’re being used.

Well, if you’re using the cookiestore for sessions, you don’t have to
worry about stale sessions anyway. The file store should be avoided
imo, the IO is simply too expensive. Database session storage is an
option, although I see little to no reason to use it when you have
something that just takes session storage away from the server.

Your database optimizations and operations can be run as a cron tab,
just call a rake task that does what it needs to do and be done with it.

Best regards

Peter De Berdt

3

in my application, i have login form. while login into the application
iam maintaning the details in session. i want to remove the stale
sessions and while removing the stale sessions i want to perform some
operattions on database . how to do this.

How are the sessions stored? The default now is Cookie store, so you
can’t
easily delete all sessions. If you’re using file store, you can just
remove
all files in the folder, if your using a DB store you can truncate the
table.

The other way is to have a version field checked/set in a filter in your
application and empty any incoming session requests if they don’t have
the
right version. It won’t delete them all immediately, but at the time
they’re being used.

Cheers,

Andy

4

On 27 Apr 2010, at 18:13, Hassan S. wrote:

Well, if you’re using the cookiestore for sessions, you don’t have
to worry
about stale sessions anyway.

? How so?

Because the session data is kept in a cookie on the client side, not
on the server in any way. The session is removed on the user’s
computer when he quits his browser. As long as you’re not storing more
than 4KB of (sensitive) data in the session (which you should never do
in the first place), it’s the least expensive session storage with the
least redundant data hanging around.

Best regards

Peter De Berdt

5

On Tue, Apr 27, 2010 at 9:38 AM, Peter De Berdt
[email protected] wrote:

Well, if you’re using the cookiestore for sessions, you don’t have to worry
about stale sessions anyway.

? How so?

Because the session data is kept in a cookie on the client side, not on the
server in any way. The session is removed on the user’s computer when he
quits his browser.

That’s irrelevant if the app in question depends on inactive sessions
being expired.

–
Hassan S. ------------------------ [email protected]
twitter: @hassan

6

On Tue, Apr 27, 2010 at 8:56 AM, Peter De Berdt
[email protected] wrote:

Well, if you’re using the cookiestore for sessions, you don’t have to worry
about stale sessions anyway.

? How so?

–
Hassan S. ------------------------ [email protected]
twitter: @hassan

7

On 27 Apr 2010, at 18:50, Hassan S. wrote:

quits his browser.

That’s irrelevant if the app in question depends on inactive sessions
being expired.

http://dev.rubyonrails.org/ticket/10751

Best regards

Peter De Berdt

8

On Tue, Apr 27, 2010 at 9:56 AM, Peter De Berdt
[email protected] wrote:

That’s irrelevant if the app in question depends on inactive sessions
being expired.

http://dev.rubyonrails.org/ticket/10751

Interesting but also irrelevant; recognizing a request for an expired
session is not the same as explicitly expiring a session and doing
any necessary cleanup.

But thanks for the reference.

–
Hassan S. ------------------------ [email protected]
twitter: @hassan