Re: [PHP] Session handlers

2004-10-02 Thread Chris Shiflett
--- Tim Van Wassenhove <[EMAIL PROTECTED]> wrote: > If others can read from your session.save_path, i'm pretty sure > they'll be able to read the credentials you use in the scripts > to connect the database too. Which makes the security argument > in this case invalid. You can store the database a

Re: [PHP] Session handlers

2004-10-02 Thread Tim Van Wassenhove
In article <[EMAIL PROTECTED]>, Ewout De Boer wrote: > > - Original Message - > From: "Shawn McKenzie" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, October 02, 2004 2:11 AM > Subject: [PHP] Session handlers > > >> Just curious, what is the advantage of using a custom

Re: [PHP] Session handlers

2004-10-02 Thread Ewout de Boer
- Original Message - From: "Shawn McKenzie" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, October 02, 2004 2:11 AM Subject: [PHP] Session handlers > Just curious, what is the advantage of using a custom session handler, > such as saving session data in MySQL? security !

RE: [PHP] Session handlers

2004-10-01 Thread Vail, Warren
I have used MySQL sessions and session handler routines to perform the following; 1. I was able to set different session timeouts for different applications as long as each application used a different session table. The garbage cleanup routines could be programmed to ignore the global session l

Re: [PHP] Session handlers

2004-10-01 Thread raditha dissanayake
Shawn McKenzie wrote: Just curious, what is the advantage of using a custom session handler, such as saving session data in MySQL? The main reason you might want to store session informaton in a database instead of in files is that you can then load balance your site across multiple servers. If