IL 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 ..
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 i
> - I have an index_html method that calls an "initializeSession" method at
> the beginning to initialize certain session variables. (Is there another
way
> to do this?)
Yes, you can use an "script to call when objects are added" method in the
transient data container related to the session in or
I have a slight correction to make (which doesn't change the message of this
posting):
> - As the new sessioning code seems to be working within the transaction
> machinery, the SESSION.set action causes the mere display of an index_html
> page (that includes a session initialization method) to b
uot;Joachim Werner" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, January 14, 2002 9:03 PM
Subject: Re: [Zope-dev] Re: Temporary Storage + Sessions + Versions: How?
> Joachim Werner wrote:
>
> > Thanks for the hint. I'll try using a versioning storag
Joachim Werner wrote:
> Thanks for the hint. I'll try using a versioning storage, though it might be
> rather inefficient I guess?
Most (all?) versioning storages are also undoing so you'll be keeping
undo data that will need to be packed away. It's also hard to manage an
undoing mounted sto
Hi!
Thanks for the hint. I'll try using a versioning storage, though it might be
rather inefficient I guess?
> > As the Temporary Storage is incompatible with versions, it seems to
> me that
> > I can not at all use any session manipulating code in a method that
> might be
>
> > called under
Joachim Werner wrote:
> As the Temporary Storage is incompatible with versions, it seems to
me that
> I can not at all use any session manipulating code in a method that
might be
> called under version control. This is very disturbing to me.
I'm sorry you're disturbed. ;-)
> Are there
