Re: [Modeling-users] Another question about sessions and EditingContexts (sorry)

[Ernesto R. <er...@si...>]

Dear S=E9bastien,

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.=20

With best regards,=20
Erny



----- Original Message -----=20
From: "Sebastien Bigaret" <sbi...@us...>
To: "Ernesto Revilla" <er...@si...>
Cc: "modeling-users" <mod...@li...>
Sent: Sunday, February 29, 2004 2:37 PM
Subject: Re: [Modeling-users] Another question about sessions and =
EditingContexts (sorry)



"Ernesto Revilla" <er...@si...> wrote:
> Dear all,
>=20
> 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=E9bastien.