Yeah... Either this or a storage that doesn't cause a version lock error when accessing an object that has been changed in a version are potential solutions.
----- Original Message ----- From: "Joseph Wayne Norton" <[EMAIL PROTECTED]> To: "Chris McDonough" <[EMAIL PROTECTED]> Cc: "Joachim Werner" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, January 14, 2002 11:53 PM Subject: Re: [Zope-dev] Re: Temporary Storage + Sessions + Versions: How? > Chris and Joachim - > > Maybe this is too simplistic of an approach ... but why not have the > session data manager automatically create a new, session data > container (temporary storage) for a given zope version. The session > data manager can be optimized for the case of no version and then when > and if needed create temporary storages on demand for a particular > version. > > - j > > > _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
