After just announcing msession, I am already getting requests for some sort of hot spare system.
OK, here is the question: how hot is hot? A periodic update, where once a minute or so, changes are batched out to the hot spare. A really hot spare where all write actions are mirrored on to the hot spare (this has bigger performance issues) A cold spare, no actual mirroring, just recreate the sessions from the web servers, and lose what was on the primary. Lastly, is redundancy a *MUST HAVE* to be useful? The reason I ask is because a lot of people use something like MySQL to handle sessions, and that isn't redundant, nor would I consider it fault tolerant. Msession is theoretically more reliable in that it doesn't use the hard disk. Depending on programming errors, it could be as reliable as the hardware and OS on which it is running. What do you all think? -- PHP Development 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]
