> A session data object timeout of "0" as set in the session data container
> means "give me completely persistent session data objects, do not expire
> them".  Set it to this, and set a high cookie timeout.  But yes, a better
> way to do something like this is to use sessioning in combination with a
> membership product.

Ah ok, yes the more I thought about it, the more I thought a Membership
system is the way to go.

> Local filesystem access won't work across ZEO clients.  The primary
> of an external data container is to provide access to a shared namespace
> between ZEO clients.  This doesn't mean someone couldn't write an
> data container implementation that uses the filesystem, however.

True. But its another option that is quick and easy for many people. I'll
put it on my interesting things to do on a rainy day list somewhere....

> As far as the difficulty of mounting goes, when I can find some time, I
> to write a mounting howto.

Thats always welcome.


Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to