durusmail: quixote-users: Session persistence for Quixote 2.0
Session persistence for Quixote 2.0
2005-05-26
2005-05-27
2005-05-27
2005-05-27
2005-05-27
2005-05-27
2005-05-27
2005-05-27
2005-05-28
2005-05-29
2005-05-29
2005-05-29
2005-05-28
2005-05-28
2005-05-29
2005-05-29
Sessions in mod_python (was [Quixote-users] Session persistence...
2005-05-29
Session persistence for Quixote 2.0
Mike Orr
2005-05-27
Titus Brown wrote:

>-> On May 26, 2005, at 5:48 PM, Titus Brown wrote:
>-> >The short version is that the SessionManager included with Quixote
>-> >is aimed at a single-process object-database backend like Durus,
>-> >and it
>-> >has been difficult for me to make it work nicely with other
>-> >backends, or
>-> >with threads.
>

I think Titus was talking about the ominous warning in the Durus docs
about "cannot be used from multiple threads in a single process".  Which
brings up a related question I've been pondering.  How do you migrate
data between Durus and ZODB?  I may want to use Durus but I'm concerned
about that thread limitation.  Not that it matters now but it may in the
future.  I notice Durus classes are persistent through a persistent
mixin, while ZODB classes are persistent through a different mixin.  If
I do need to port a Durus database to ZODB, do I have to create a
parallel tree of objects and copy the attributes from each object to the
other, or is there an easier way?


reply