Il pinguino volante wrote:
(There were some erroros in the previous email, I'm sorry)
Hi to all.
I have to realize an authentication system for a lot of users.
I heard that someone uses to store session states (?) into a database.
I'd like to know how and, expecially, WHY to do it and what's
Sam Stelfox wrote on 2009-10-06 18:09:
If you are distributing your application over multiple servers, using a
database for session tracking allows a user to continue there session
regardless of which server their request bounces too. It prevents the
need for 'sticky' network connections which
On 10/6/09 10:26 AM, "Il pinguino volante" wrote:
> I have to realize an authentication system for a lot of users.
>
> I heard that someone uses to store session states (?) into a database. I'd
> like to know how and, expecially, WHY to do it and what's would be better
> (considering that I CANN
If you are distributing your application over multiple servers, using a
database for session tracking allows a user to continue there session
regardless of which server their request bounces too. It prevents the
need for 'sticky' network connections which time out anyways. Databases
can make sc
4 matches
Mail list logo
