Marc Richards wrote:
Rasmus Lerdorf wrote:
Jani Taskinen wrote:
On Sun, 14 Aug 2005, Ilia Alshanetsky wrote:
If apc comes bundled then it includes apc_store() and apc_fetch() this
is pretty much $_MEMORY with a few tweaks.
Yes, but that is restricted to one server installations.
I need such a 'global session' that is available with multiple
front-end servers..ie. using DB as session storage.
I am confused. What are you proposing here? That we write a
multi-server memory-based datastore? That's a project in itself and
quite beyond the scope of PHP. It would seem to me like a replicated
database setup with decent query caching solves this problem nicely.
-Rasmus
How about an implementation with multiple possible backends ala
session.save_handler?
It could use "files" or "apc" by default, or optionally use something
like "mm", "msession" or "mysql" depending on the user's needs.
Marc
Oops. Hit send a little early.
Just to clarify, the value of adding this extra layer of complexity
would be that developers could write apps that persitently store and
retrieve data at an application level without worrying about
portability. It would then be up to the server admin to choose the
appropriate backend based on their own requirements such as speed,
platform, security, or multi-server configuration.
I would envision it working in a manner very similar to how sessions
work now, including the use of a user-configurable an APPLICATION_ID to
prevent colisions.
Marc
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
