On Mon, 2003-03-17 at 20:34, John Eikenberry wrote:
John Eikenberry wrote:
Toby Dickenson wrote:
Read conflicts occur if a change is committed in between the start of a
transaction, and the transaction needing to load the object. A workaround to
reduce the number of read
On Mon, 2003-03-17 at 15:02, Dieter Maurer wrote:
You know that we use a Transience implementation with minimal
(and not very essential) administrative data which
is immune to inconsistencies and can be used across several
ZEO clients (although we do not use that).
We have good experience
On Tuesday 18 March 2003 3:24 pm, Chris McDonough wrote:
Our live sessions code uses the sessions about half to two-thirds of the
way through the transaction. Given what can happen in that first half,
there is easily plenty of time for read conflicts. I think I might be
able to move our
Fred L. Drake, Jr. wrote:
I'm planning to merge the new-install-branch efforts recently
discussed on this list into the Zope 2 trunk tomorrow. There will be
things to do after the merge, but the basic functionality will be more
easily testable and easier to contribute to.
Will I have to change
Chris Withers writes:
Will I have to change the way Zope is built and/or the etsts are run?
Yes.
If so, where could I find otu what they now need to look like?
There is a scenario for Linux in the newinstallbranch.xml in
Packages/TestScripts; I'll test it again before the merge takes
[Fred L. Drake, Jr.]
I'm planning to merge the new-install-branch efforts recently
discussed on this list into the Zope 2 trunk tomorrow.
...
http://mail.zope.org/pipermail/zope-dev/2003-March/018999.html
Perhaps the most immediate change is that the Windows tests may become
completely
Today you are guaranteed that your transaction reads a consistent initial
state of A and B. That is, there is no chance that you only see half the
changes of a recent transaction that modified both.
Yes, it is possible for one transaction to modify A and a concurrent
transaction to
On Tuesday 18 March 2003 6:12 pm, Chris McDonough wrote:
I'm
thinking that I also may just need to move the housekeeping duties to a
separate scheduled thread that only happens when the system is not
busy (e.g. when the asyncore poll select timeout is reached maybe) in
order to reduce the
On Tue, 2003-03-18 at 14:01, Toby Dickenson wrote:
On Tuesday 18 March 2003 6:12 pm, Chris McDonough wrote:
I'm
thinking that I also may just need to move the housekeeping duties to a
separate scheduled thread that only happens when the system is not
busy (e.g. when the asyncore poll
I wrote:
I'll send a note to the zope-coders list before I actually start the
merge. For a description of the changes (and the ensuing discussion),
refer to this thread:
http://mail.zope.org/pipermail/zope-dev/2003-March/018999.html
The unit tests work on Windows for the branch at
Marco Catunda wrote at 2003-3-17 19:39 -0300:
I have tried call a function via XMLRPC with * and ** args
with no success!
XMLRPC is a cross language technology.
It does not support Python specialities such as * and ** arguments.
Dieter
___
Fred L. Drake, Jr. writes:
I'm starting the mechanics of the merge into the trunk now; I'll send
another email when the merge is complete.
I'm done. The new-install-branch is now dead.
-Fred
--
Fred L. Drake, Jr. fred at zope.com
PythonLabs at Zope Corporation
Chris McDonough wrote:
On Mon, 2003-03-17 at 20:34, John Eikenberry wrote:
The KeyErrors happen under similar circumstances to the ReadConflictErrors.
The significant difference being that the KeyErrors happen after the
transience timeout has occured. When I am running with the
Small problem.
The 'make install' step creates files in the source tree. It probably
shouldn't do this, because if you want to do this as root (sudo make
install to install under /usr/local, say), these file are created as
root. This is impolite more than anything else.
The build and install
Adrian van den Dries writes:
The 'make install' step creates files in the source tree. It probably
shouldn't do this, because if you want to do this as root (sudo make
install to install under /usr/local, say), these file are created as
root. This is impolite more than anything else.
On March 19, Fred L. Drake, Jr. wrote:
How important is it to support out-of-place builds?
http://dev.zope.org/Wikis/DevSite/Proposals/InstallationAndConfiguration
configure; make; make install source package installation process
and some form of INSTANCE_HOME installation thereafter.
Adrian van den Dries writes:
On March 19, Fred L. Drake, Jr. wrote:
How important is it to support out-of-place builds?
http://dev.zope.org/Wikis/DevSite/Proposals/InstallationAndConfiguration
Ok, I'm too tired to read that now; I'll look at it tomorrow between
meetings.
configure;
On March 19, Fred L. Drake, Jr. wrote:
(The Quick Start section uses an abbreviated procedure that
creates an instance home in the source directory.)
It calls configure with --prefix=/where/to/install/zope which is then
unused.
a.
--
Adrian van den Dries [EMAIL
18 matches
Mail list logo
