hi, 2009/12/18 Daniel Pittman <[email protected]>: > justin randell <[email protected]> writes: >> 2009/12/18 Daniel Pittman <[email protected]>: >>> justin randell <[email protected]> writes: >>>> 2009/12/17 Daniel Pittman <[email protected]>: > > [...] > >>> Anyway, I am curious to know if that is still true: if I can't modify the >>> PHP code, can I store sessions in a database these days? >> >> ah, now i see what you mean. yes, its still true, unless you install a php C >> extension that defines a session.save_handler for you to write session info >> to a database, then you need php code. > > I guess the last, obvious, question is: has someone written a standard C > extension that does that, targeting MySQL or PostgreSQL? Google didn't give > me a convincing answer, and I am hoping an expert can. :)
no, not that i know of. the PECL memcache extension defines a session save handler, which is a very fast, scalable way to do it, provided you don't mind session data going away when your memcache instances do... personally, i'd be more interested in an extension that used a fast, scalable key-value style db as a session backend, rather than a relational db with all those fancy ACID features you never use when pulling out and sticking in session data. for example, django has a session backend for tokyo cabinet via tokyo tyrant: http://github.com/ericflo/django-tokyo-sessions/ python people have all the fun ;-) cheers justin -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
