[EMAIL PROTECTED] wrote: > The problem with using databases are they they are expensive and they are > slow. > > A generalized PostgreSQL session manager would be cool, I have actually > been thinking about such an extension. Using the schema from the PG > msession plugin, it would be fairly easy. Alas, the problems with > PostgreSQL as a session manager are many. MySQL is just as bad, but for > different reasons. :-) > > It is because the databases fall flat as session managers that I wrote > msession in the first place. > I agree that msession is better than using MySQL or PostgreSQL as a session manager. However, most people who use PHP on web farms already have some sort of database set up, so it seems logical to me to be able to use it for storing sessions. MySQL actually isn't too bad, as long as you use HASH (in-memory) tables.
>> >> Right now I don't run any web farms, but I used to work for a company >> with 125+ web servers, so I understand the problem. > > 125??!! All serving the same content? All maintaining a coherent > environment? What did you use for session data? MySQL. They weren't all serving the same content, but almost all of them were sharing a session. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
