Jens Vagelpohl wrote:
IMHO if this is just UI changes that improve usability it should be OK
to flout the rules a bit. The rules are there to ensure code quality
and stability in a release branch - I doubt small UI changes endanger
those.
Beware the slippery slope to hell, paved with
I've done a big checkin to switch practically everything to the new-
style (actually they're 5 years old) security declarations.
I'd appreciate if another set of eyes could double-check everything;
while I've taken a number of steps to ensure I didn't make mistakes
you never know...
Conflicts and how they interact with the database and sessioning machinery
is my hot button right at the moment )-: I Hope I have not
included too much information.
I ran a quick report and we see about 1000 conflicts per hour at
about 12 hits per hour. These are order of magnitude
[Dennis Allison]
...
Conflict errors are not always errors.
At the ZODB level, an unresolved conflict always raises an exception.
Whether such an exception is considered to be an error isn't ZODB's
decision -- that's up to the app. My understanding (which may be
wrong) is that Zope tries up
On Nov 21, 2005, at 2:10 PM, Dennis Allison wrote:
Conflicts and how they interact with the database and sessioning
machinery
is my hot button right at the moment )-: I Hope I have not
included too much information.
I ran a quick report and we see about 1000 conflicts per hour at
about
These are order of magnitude numbers and are
highly variable. The 1% number is way bigger than I am
comfortable with
although I have no basis to scale my expectations. I'd be much
happier were
it a couple of orders of magnitude smaller.
I would be too. It's considerably difficult when
On Mon, 21 Nov 2005, Chris McDonough wrote:
On Nov 21, 2005, at 2:10 PM, Dennis Allison wrote:
Conflicts and how they interact with the database and sessioning
machinery
is my hot button right at the moment )-: I Hope I have not
included too much information.
I ran a quick
Dennis Allison wrote:
*** you are correct -- this is the easy hack on the event.log. It's much
harder to know how many make it out to the user. We have an associated
bug in the MySQL interface which generates threading errors, apparently
triggered by a conflict error and the subsequent
[redirected to zope-dev]
John Ziniti wrote:
Back in June 2004, I had the following problem:
http://mail.zope.org/pipermail/zope/2004-June/151436.html
http://mail.zope.org/pipermail/zope/2004-June/151492.html
http://mail.zope.org/pipermail/zope/2004-June/151497.html
Hello, Florent.
you wrote 22 íîÿáðÿ 2005 ã., 2:13:16:
BTW does someone have a handy script to provoke conflict errors on a
naked Zope?
Using http://www.zope.org/Members/kvas/ZAK ( it need some patch for
zope 2.8) ( you need to read some manual about ZAK )
in 1 browser window try the
10 matches
Mail list logo
