method.
Hope this makes more sense than my last post.
Thanks again!
Matt
-Original Message-
From: Angelo Zanetti [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 5:45 AM
To: [EMAIL PROTECTED]
Subject: RE: [PHP] dreaded sessions
just
just out of interest sake why do you use INNODb? cant you use the normal (no
transaction support) MySQL DB??
-Original Message-
From: Greg Donald [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 2:04 AM
To: [EMAIL PROTECTED]
Subject: Re: [PHP] dreaded sessions
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian V Bonini wrote:
| Kind of funny... Back before PHP had sessions this was how everyone did
| it and everyone wished for session support in PHP, now that it's had it
| for a while :)
I hear ya. I recall a job interview in like 1999 or something
sorry i missed this thread, but what seems to be the problem with php
sessions ? I had to use phplib sessions on the works php3 server, which one
is better disk based sessions or database based sessions ? I have no
problem whatsoever with 60 concurrent users on a php session based system
but what a
On Mon, 2004-01-19 at 17:38, Greg Donald wrote:
> I'd say it has something to do with you transactions. Can you duplicate
> the errors using the same code on a system where the Innodb transactions
> do not require committing?
>
> Here is my own drop-in PHP session handling code if you care to co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Horner wrote:
| Simply here is my problem:
|
| After logging into the system, I set a session with information for
| the Username and Password for verifiying
| the user's login into the system, that way I don't have to
| continually ask
6 matches
Mail list logo
