to be honest... a while back, i set my sessions to be flat-file based, just because I didn't want to deal with the stuff you're going through ;)
i had sessions in postgres at one time, but i don't think they were beaker based. it was a tie-in to some mod_perl legacy apps. for them i did this paradigm: session_write to memcached , if there is any data-change other than accessinfo, wrte to postgres too session_read from memcached, failover to postgres, failover to new session a cronjob would clear out old session stuff from both . it was really fast , because the timestamp column was just 1 line. i don't recall how the bdb / dbm stuff works. you may have to inspeact/loop sessions. but it should still be lightning fast. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
