if yours only storeing one or two variables in a db, dont mind writing
either functions to store all this in the db, or having 5-10 lines of code
per page to this then fine. But sessions are so simple...
<?
session_start();
$test[] = '123';
$test[] = '456';
$test[] = '789'
$someclass = new product_class();
$SessionID = time();
session_register('test');
session_register('someclass');
session_register('SessionID');
?>
three lines of code, I can store text, arrays, class's all in three lines of
code, four if you count session_start(). now one those vars have been
registered you no longer have to execute session_register() everytime you
change something, its all automatic.
I use sessions because they are so simple. I cant say for sure but a good
guess would be that file I/O from sessions would be less overhead then
mysql_db overhead.
--
Chris Lee
Mediawaveonline.com
[EMAIL PROTECTED]
"Noel Akins" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Would there be any point in using php sessions if you aren't using
cookies?
> You have to store login info anyway, why not just use a temp table to
store
> transaction info and write to the database at the end of a session? From
> what I've read on sessions, you have to use cookies
> thanks
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
