Re: Another question about sessions and EditingContexts (sorry)

"Ernesto Revilla" <[email protected]> Mon, 1 Mar 2004 13:27:18 +0100
Newsgroups gmane.comp.python.modeling
Message-ID <001b01c3ff89$7910ea60$0100a8c0@servidor>
Dear Sébastien,

Yes, actually I have time to do some testing in a test environment (no production) with sqlite and Postgresql. (And I'm sorry I couldn't help you with python metaclasses in the past.) I'm also very interested in optimistic locking. 

With best regards, 
Erny



----- Original Message ----- 
From: "Sebastien Bigaret" <[email protected]>
To: "Ernesto Revilla" <[email protected]>
Cc: "modeling-users" <[email protected]>
Sent: Sunday, February 29, 2004 2:37 PM
Subject: Re: [Modeling-users] Another question about sessions and EditingContexts (sorry)



"Ernesto Revilla" <[email protected]> wrote:
> Dear all,
> 
> as stated in the documentation, section 6. Integration in an application,
> using an application server, actually it is recomended to use a fresh
> EditingContext for each session. But it states also, that changes made
> permanent with saveChanges will not be visible to other EditingContexts. Is
> the also the case for Zope ZEditingContextSessioning? Could anybody tell me
> in which environment she/he uses modeling, and how he treats the
> EditingContexts? (I'm looking for application server like uses.)

  This is the case in every multi-ECs environment, including Zope and
  ZECSessioning.

I currently have the intention of solving that longstanding issue of
synchronizing ECs --and this is a prerequisite for optimistic
locking. Would you have some time testing patches on that topic?

-- Sébastien.





-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=click