Hi all,
I discovered a problem when using CAP::Session and CAP::DBH at the same
time. When I first started testing CAP::Session, I was not getting any
session data written to the database unless I manually added a
$self->session->flush to cgiapp_postrun. I didn't really want to do
that because I have some requests that don't require authentication and
this would generate a session for each of those because it goes around
the lazy loading that CAP::Session normally does. After some
experimenting, I found that if I manually created a database handle and
passed it to CAP::Session instead of using $self->dbh like I normally
do, everything worked.
So, I'm guessing what's happening is that the database handle inside of
CAP::DBH is getting DESTROYed before the session object. Is there any
good way to get around this?
Thanks!
Curtis H.
