ID:               20449
 Comment by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
 Status:           Feedback
 Bug Type:         Session related
 Operating System: redhat 7.3
 PHP Version:      4.3.0-dev
 New Comment:

The php version I'm using at the moment is
PHP Version 4.4.0-dev

Any other info can be found here.
http://www.t-shirtking.com/temp/phpinfo.php


Previous Comments:
------------------------------------------------------------------------

[2002-11-15 19:32:38] [EMAIL PROTECTED]

Can you add _short_ example script here that shows the problem, as I'm
using sessions a lot and never have had any problems with them. Albeit
I haven't tried to overload them too much either. Maybe you're doing
something that isn't really been thought about when the session
extension was written?


------------------------------------------------------------------------

[2002-11-15 19:26:09] [EMAIL PROTECTED]

Please put correct version number in the report..
I assume it's 4.3.0-dev but if it's something else, please
change it.


------------------------------------------------------------------------

[2002-11-15 16:35:46] [EMAIL PROTECTED]

I've experienced the same problem, on various platforms. SPARC Solaris
8 with PHP 4.2.2, Intel Linux 2.4 with PHP 4.2.3, and RedHat Alpha
Linux 2.4 with PHP 4.2.3.  

However I'm not using it in the context of a shopping cart, my
application is that of a "Checksheet" that we use to mark off Quality
Assurance items. The Checksheet is large so I store the form contents
in a session. They can move through all kinds of menus and parts of the
Checksheet and the work is stored entirely in a session. About 8 people
use this Checksheet system throughout the day 7 days a week, about once
a day suddenly the Checksheet system will say they aren't logged in,
and when they relogin in, their work is gone. I've implemented a quick
and dirty save to database feature for long term storage and I've
encouraged my users to frequently save. The save merely serializes the
Checksheet object that is normally stored in a session, and saves it to
a database.

------------------------------------------------------------------------

[2002-11-15 14:15:51] [EMAIL PROTECTED]

Quick question.

What should session.save_handler be in the php.ini file when using my
own mysql session handlers?  Should it remain files or should it get
set to user to make the session_set_save_handler work properly?  The
documentation is somewhat unclear on this.

------------------------------------------------------------------------

[2002-11-15 13:58:51] [EMAIL PROTECTED]

I am already using the save handler to use my own mysql backend.  

Please don't close this bug again.  I am using CVS from a build on
11-14-2002.  I still get random session failure.  

Here is a list of other bugs that are related to this.
Bug #19029
Bug #17846
Bug #19972
Bug #19022

As far as I can tell, these other bugs were never fully resolved.

BTW, while I allow php to set a cookie, I don't use it at all.  I
manually set session_id by using the session passed via the url.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/20449

-- 
Edit this bug report at http://bugs.php.net/?id=20449&edit=1

Reply via email to