Session behavior, Survey
| From: | mlwmohawk at mohawksoft dot com | Date: | Sun, 10 Nov 2002 20:27:53 +0000 |
| Subject: | Session behavior, Survey | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-90734@lists.php.net to get a copy of this message | ||
I want to conduct a survey of the various behaviors of "sessions" as used
by PHP.
Specifically, I am wrapping up some new features on msession, and I would
like to come up with a more realistic test suite for the system. Some of
the questions are obviously hard to nail down, but any input would be
greatly appreciated. I want to hear about what happens in your system.
About how many times is a session accessed after being created?
Do accesses of the session data string always result in an update?
About how large is the session string created by the PHP session manager?
Do sessions get explicitly deleted or do they usually just timeout?
What is a "typical" session transaction? i.e. I assume it is a
read/followed by a write, and a create on the first connection, and either
an explicit delete or expiration at the end.
Feature questions:
How "opaque" can a session be? i.e. would you need the session data
available to other applications outside the session manager?
Thanks in advance,
Mark.
P.S.
Current features targeted for 1.2:
ASCII transport for heterogenous cluster designs.
Thread pool option for enhanced performance.
Enhanced PostgreSQL plugin.
Local binary execution
Enhanced administration tools.
Enhanced plugin support.
Minor bug fixes