Hi again,
Am Mittwoch, den 26.04.2006, 08:05 +0200 schrieb Christian Theune:
> I remembered there was a fix like that. Unfortunately that fix was
> ported to the 3.6 branch actually. I'm poking around myself a bit more.
>
> What I found right now is that BaseStorage accesses an attribute "_oid"
Hi,
Am Dienstag, den 25.04.2006, 23:50 -0400 schrieb Tres Seaver:
>
> Smells like a fix didn't get forward-ported somehow -- that looks like
> the same error I helped Tim find and fix for Zope 2.
>
> CC'ing the ZODB list just in case anyone there has a better memory.
> Here is the NEWS.txt entry
Hi Rodrigo! Great post on this. You provide an insightful and compelling
summary of what can be accomplished. Add on top of this, the things that
twisted "just does" like SSL or SSH out of the box and we can also have
the security issue beat. Jim, what do you think? Do you think you could
give
You probably already know all of these, but just in case ...
[ Jim Fulton ]:
---
|
| I am strongly against linking ZEO to an application's main loop.
Twisted performs better if the protocols build upon it rely on its
reactor (asynchronous loop). That means breaking long computations
I must say I'm not an expert on all things ZODB/ZEO, but what I meant by
ownership is the management of persistent objects. The cache management
logic of ZODB can the way I understand it "ghostify" objects, what happens
if I insert an object from one ZODB (using ClientStorage) into another
Arve Knudsen wrote at 2006-4-25 17:32 +0300:
> ...
>How should I ensure local
>ownership of objects from the ClientStorage, by deep copying them?
The ZODB does not have any "ownership" concept.
Zope, on the other hand has two: executable ownership
and "local role" ownership.
Executable owner
Hi Jim. My experience has been in running a single selectreactor in an
app together with its own main loop.
I found a patch on google to allow multiple selectreactors but have not
seen the patch applied to svn or attempted the change in twisted as yet.
I have emailed the maintainer to ask abou
[Sidnei da Silva]
> It's a bad disk block situation. No blame on Zope. Getting a new
> disk.
That's refreshing -- most people would claim that ZODB destroyed their
disk ;-) These are the times you're glad you made backups, eh?
http://zope.org/Wikis/ZODB/FileStorageBackup
On Mon, 24 Apr 2006 22:17:17 +0300, Dieter Maurer <[EMAIL PROTECTED]>
wrote:
Arve Knudsen wrote at 2006-4-23 22:44 +0300:
I already use ZODB as a local persistency service for my Python
application, now I'm considering ZEO as a distributed data source. The
thing is I don't want to keep my loc
On Tue, Apr 25, 2006 at 10:22:25AM -0300, Sidnei da Silva wrote:
| Any hint to what can be done to recover from this situation?
It's a bad disk block situation. No blame on Zope. Getting a new
disk.
--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856
Sidnei da Silva wrote:
Got the following exception while doing some work on a Zope instance
here. It's the first time I see such error.
* Module ZEO.ClientStorage, line 746, in load
* Module ZEO.ClientStorage, line 769, in loadEx
* Module ZEO.ServerStub, line 192, in loadEx
* Mod
David Pratt wrote:
...
Is there is any strong opposition to using the twistd daemon for a
twisted zeo service?
I am strongly against linking ZEO to an application's main loop.
If twisted supports using multiple independent main loops, then it would
be an option.
Then the possible issues are:
Florent Guillaume wrote:
Huh, I thought you were talking about the ZEO client, ClientStorage, not
the ZEO server.
For the ZEO server I don't see the point of changing it, it works well.
OTOH a ClientStorage has to integrate with the other servers in Zope,
and that's the one that would benefi
Florent Guillaume wrote:
Hi,
Jim Fulton wrote:
Log message for revision 67595:
Added compatibility for old pickles.
Modified:
Zope3/branches/jim-adapter/src/zope/app/component/tests/test_registration.py
+# Work around a bug in ZODB
+# XXX fix ZODB
+class FileStorage(ZODB.FileStorage.Fi
Hi,
Jim Fulton wrote:
Log message for revision 67595:
Added compatibility for old pickles.
Modified: Zope3/branches/jim-adapter/src/zope/app/component/tests/test_registration.py
+# Work around a bug in ZODB
+# XXX fix ZODB
+class FileStorage(ZODB.FileStorage.FileStorage):
+
+def new
Florent Guillaume wrote:
On 25 Apr 2006, at 15:23, Jim Fulton wrote:
Florent Guillaume wrote:
[Ccing zodb-dev]
On 25 Apr 2006, at 15:09, David Pratt wrote:
The protocol is simple yes, but the iteractions w.r.t threading
are sometimes subtle.
Hi Florent. This could be set up using a t
On 25 Apr 2006, at 15:23, Jim Fulton wrote:
Florent Guillaume wrote:
[Ccing zodb-dev]
On 25 Apr 2006, at 15:09, David Pratt wrote:
The protocol is simple yes, but the iteractions w.r.t threading
are sometimes subtle.
Hi Florent. This could be set up using a twisted's application
object
Got the following exception while doing some work on a Zope instance
here. It's the first time I see such error.
* Module ZODB.Connection, line 704, in setstate
* Module ZODB.Connection, line 760, in _setstate
* Module ZODB.serialize, line 495, in setGhostState
* Module ZODB.serial
Florent Guillaume wrote:
[Ccing zodb-dev]
On 25 Apr 2006, at 15:09, David Pratt wrote:
The protocol is simple yes, but the iteractions w.r.t threading are
sometimes subtle.
Hi Florent. This could be set up using a twisted's application
object so that you have a twisted app using a twist
[Ccing zodb-dev]
On 25 Apr 2006, at 15:09, David Pratt wrote:
The protocol is simple yes, but the iteractions w.r.t threading
are sometimes subtle.
Hi Florent. This could be set up using a twisted's application
object so that you have a twisted app using a twisted .tac. I guess
this coul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Apr 2006, at 09:01, Thomas Guettler wrote:
I think it is a bug.
If you think there is a bug please use the collector:
http://www.zope.org/Collectors/Zope
Email gets lost and forgotten, it is unsuitable for reporting bugs.
jens
-BEGI
Hi,
We just had this in data.fs.lock:
831
5
The server had an unclean shutdown. The old PID was
five digits long and was overridden by "831\n". We use
an old version of ZODB, but I looked at:
http://svn.zope.org/ZODB/trunk/src/ZODB/lock_file.py?view=markup
and the lockfile is not truncated in
22 matches
Mail list logo
