I haven't used a database backend for sessions, so I couldn't honestly say, but I'd certainly try it. Think of the overhead of using a RDBMS, as opposed to a simpler method. I could be wrong, but I think it's at least worth considering.
And if you need something accessible by multiple machines, like I mentioned, there's memcached, which is designed for this sort of thing to begin with (and easy to set up, too, based on my brief experimentation with it).
On the other hand, if it turns out that I'm wrong or if someone else knows better, feel free to tell me, too. | [reply] |
Yeah, I read that whole page on memcached and it looks really good, however, it seems that if you do a lot of updating the table, which we do a whole lot of because of the websites user activity, it may not be a good fit, also it talks about servers with a HUGE resource like 32+ Gigs, we have maybe like 8 to 10 gigs, I know it says we can limit it to like 3 gigs, so that may not be bad, but I don't know if it would be good or not, YET...
I am still interested how others use session management for a lot of page views and members logging in and doing a lot of activity, such as purchases, viewing invoices, requesting commisssions, viewing their commission accounts, signing up referals and many many other things.
Thank you,
Rich
| [reply] |