Greg Donald wrote:
On Wed, 16 Feb 2005 09:36:26 -0800 (PST), Richard Lynch [EMAIL PROTECTED]
wrote:
It's literally an hour's work to alter the code to use MySQL to store the
sessions instead of the hard drive.
Not really, maybe 5 minutes.. here's the code:
The code misses one important thing -
On Fri, 18 Feb 2005 08:56:59 +0100, Marek Kilimajer [EMAIL PROTECTED] wrote:
The code misses one important thing - row locking. For concurent
requests, sess_open must block until the first request does
sess_close(). So you need to use InnoDB's row locking or
application-level GET_LOCK() and
[EMAIL PROTECTED] wrote:
On 16 Feb 2005 Richard Lynch wrote:
Use the exact same session stuff you have now and just dump the
serialized data into SQL using the 5 functions for session handling.
Oh, OK, that's what you meant about the 5 functions. I am not sure of
the advantage to that,
[EMAIL PROTECTED] wrote:
On 15 Feb 2005 Richard Lynch wrote:
Throw an ab (Apache Benchmark) test at it and find out.
Don't just guess or sit there wondering.
You could run test in about the time it took to compose this email --
Perhaps if you are already familiar with ab, which I'm not
On Wed, 16 Feb 2005 09:36:26 -0800 (PST), Richard Lynch [EMAIL PROTECTED]
wrote:
It's literally an hour's work to alter the code to use MySQL to store the
sessions instead of the hard drive.
Not really, maybe 5 minutes.. here's the code:
Make the table in your database:
CREATE TABLE
On 16 Feb 2005 Richard Lynch wrote:
Use the exact same session stuff you have now and just dump the
serialized data into SQL using the 5 functions for session handling.
Oh, OK, that's what you meant about the 5 functions. I am not sure of
the advantage to that, actually something I've
Greg Donald wrote:
On Mon, 14 Feb 2005 16:03:10 -0500, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I have a multi-page form which I build up and store in session
variables. The data saved includes all an internal list of items on
the form (derived from a database table), all the form field
On Tue, 15 Feb 2005 13:01:45 -0800 (PST), Richard Lynch [EMAIL PROTECTED]
wrote:
If you have to choose between a meaningful variable name and performance
considerations, buy more hardware! :-)
The cost you'll save in the long run for code maintenance will make it
worth it.
Comments in the
On 15 Feb 2005 Richard Lynch wrote:
Throw an ab (Apache Benchmark) test at it and find out.
Don't just guess or sit there wondering.
You could run test in about the time it took to compose this email --
Perhaps if you are already familiar with ab, which I'm not ... and if
the server
On 15 Feb 2005 Greg Donald wrote:
If you have to choose between a meaningful variable name and performance
considerations, buy more hardware! :-)
The cost you'll save in the long run for code maintenance will make it
worth it.
Comments in the code make using short session variable
I have a multi-page form which I build up and store in session
variables. The data saved includes all an internal list of items on
the form (derived from a database table), all the form field specs
(derived from the internal item list), the data for the fields (from
another table), default
[EMAIL PROTECTED] wrote:
I have a multi-page form which I build up and store in session
variables. The data saved includes all an internal list of items on
the form (derived from a database table), all the form field specs
(derived from the internal item list), the data for the fields (from
I have a multi-page form which I build up and store in session
variables. The data saved includes all an internal list of items on
the form (derived from a database table), all the form field specs
(derived from the internal item list), the data for the fields (from
another table), default
On Mon, 14 Feb 2005 16:03:10 -0500, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I have a multi-page form which I build up and store in session
variables. The data saved includes all an internal list of items on
the form (derived from a database table), all the form field specs
(derived from
14 matches
Mail list logo
