[Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-27 Thread Dieter Maurer
Jan-Ole Esleben wrote at 2005-12-16 12:40 +0100: > ... >However, as I see it, the problem is that what Zope actually _is_ >(i.e. mostly the ZODB) is an unhealthy way of coupling data and >implementation Coupling data and behaviour (what you might call "implementation") is the main feature of objec

Re: [Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-18 Thread Michael Dunstan
On 12/19/05, Jan-Ole Esleben <[EMAIL PROTECTED]> wrote: > However, even if > it is only the docs that are lacking I think it would be sensible to > acknowledge that as a problem. Zope 3 is the literate child of Zope 2. ___ Zope maillist - Zope@zope.org

Re: [Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-18 Thread Michael Dunstan
On 12/19/05, Jan-Ole Esleben <[EMAIL PROTECTED]> wrote: > > Little bit tricky to try out as testers need to guess what all the > > missing code is. > > Any standard persistent ZOPE product wrapped around this will do. > These are the only methods in a ZOPE product that inherits from Item, > Persist

Re: [Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-18 Thread Jan-Ole Esleben
> Little bit tricky to try out as testers need to guess what all the > missing code is. Any standard persistent ZOPE product wrapped around this will do. These are the only methods in a ZOPE product that inherits from Item, Persistent, RoleManager and Implicit. > Also, for this kind of code demon

Re: [Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-18 Thread Michael Dunstan
On 12/19/05, Jan-Ole Esleben <[EMAIL PROTECTED]> wrote: > > > 1. In the example, just setting _p_changed=1 does _not_ lead to a > > > conflict error. With the ineffectual code above it (that never gets > > > executed) it _does_. So there _is_ some implicit magical stuff going > > > on and ZOPE trie

Re: [Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-18 Thread Martijn Pieters
On 12/18/05, Jan-Ole Esleben <[EMAIL PROTECTED]> wrote: > > I strongly doubt it. Zope does not "inspect code". There must be a > > problem in your testing. Note that if self.a is a standard list, the > > self.a.append(1) doesn't have any impact on the persistence mechanism or > > transactions eithe

Re: [Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-18 Thread Jan-Ole Esleben
> > 1. In the example, just setting _p_changed=1 does _not_ lead to a > > conflict error. With the ineffectual code above it (that never gets > > executed) it _does_. So there _is_ some implicit magical stuff going > > on and ZOPE tries to take care that only subobjects change (but > > incompletely

[Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-18 Thread Florent Guillaume
Jan-Ole Esleben wrote: security.declareProtected("Use TestPChanged", "test_internal") def test_internal(self, args=None, args2=None): "Called by test via XML-RPC" if args2: self.a.append(1) self._p_changed = 1 if not args: import xmlrpclib s = xmlrpclib

[Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-18 Thread Florent Guillaume
Jan-Ole Esleben wrote: Yes. You said "different sets of data". That reasonably means different objects. If it doesn't, yuo need to take a long hard look at your object hierarchy. Simply not true. What if I have a field titles (that is a hash of titles to Book objects) and a field comments (tha

Re: [Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-16 Thread Jan-Ole Esleben
Thanks, I will definitely look into that for my immediate problems. Ole 2005/12/16, Michael Haubenwallner <[EMAIL PROTECTED]>: > Jan-Ole Esleben wrote: > > > Thanks; this is a problem we are well aware of. Our solution is to > > increase the amount of workers, obviously. > > > > However, I'm incr

[Zope] Re: Zope Persistence (was: XML-RPC within ZOPE)

2005-12-16 Thread Michael Haubenwallner
Jan-Ole Esleben wrote: Thanks; this is a problem we are well aware of. Our solution is to increase the amount of workers, obviously. However, I'm increasingly getting a feeling that for a rather big range of unlikely situations that are nonetheless to be expected, Zope doesn't work _at all_. In