Christian Theune wrote:
Traceback (most recent call last):
File ZODB3-3.9.3-py2.6-linux-i686.egg/ZEO/zrpc/connection.py, line
581, in handle_request
ret = meth(*args)
File gocept.zeoraid-1.0b6-py2.6.egg/gocept/zeoraid/storage.py, line
219, in history
assert version is ''
On Thu, Nov 19, 2009 at 5:38 PM, Chris Withers ch...@simplistix.co.uk wrote:
Chris Withers wrote:
Jim Fulton wrote:
I'm fine with change the storage server to pass the history size
argument as a keyword parameter.
Okay, but where is the Z309 equivalent of ZEOStorage308Adapter's history
Jim Fulton wrote:
What's wrong with the original idea of having the server pass the size
as a keyword parameter? The ZEO protocol is irrelevant.
Okay, from the top:
So, a ZODB 3.9.3 ClientStorage calls the ServerStub's history method, this
does an rpc call:
self.rpc.call('history', oid,
Jim Fulton wrote:
So why not add a history method to ZEOStorage that passes size as a
keyword argument?
I don't know what ZEOStorage is...
zrpc.connection.Connection appears to despatch direct to the storage,
please correct me if I'm wrong.
In this case, that's a RAIDStorage. It doesn't have
On Thu, Nov 19, 2009 at 6:07 PM, Chris Withers ch...@simplistix.co.uk wrote:
Jim Fulton wrote:
So why not add a history method to ZEOStorage that passes size as a
keyword argument?
I don't know what ZEOStorage is...
Then we shouldn't be having this conversation.
Jim
--
Jim Fulton
Jim Fulton wrote:
On Thu, Nov 19, 2009 at 6:07 PM, Chris Withers ch...@simplistix.co.uk wrote:
Jim Fulton wrote:
So why not add a history method to ZEOStorage that passes size as a
keyword argument?
I don't know what ZEOStorage is...
Then we shouldn't be having this conversation.
I'm
On 11/20/2009 01:07 AM, Chris Withers wrote:
Jim Fulton wrote:
On Thu, Nov 19, 2009 at 6:07 PM, Chris Withersch...@simplistix.co.uk
wrote:
Jim Fulton wrote:
So why not add a history method to ZEOStorage that passes size as a
keyword argument?
I don't know what ZEOStorage is...
See
Christian Theune wrote:
There's a size argument following the version which probably is not
being passed as a keyword argument so it looks like a slight API
incompatibility. I wonder whether ZEORaid should hack around that or
whether the caller should be changed.
Hmm... looking more closely
On 11/02/2009 10:47 AM, Chris Withers wrote:
Christian Theune wrote:
There's a size argument following the version which probably is not
being passed as a keyword argument so it looks like a slight API
incompatibility. I wonder whether ZEORaid should hack around that or
whether the caller
Christian Theune wrote:
Would anyone object if I wrote a test and fixed this on the 3.9 branch
of ZODB? I'm not really sure what to do about the trunk...
I think that's the best idea. It's not exactly part of the policy of
supporting old protocols but if we want to support and encourage 3rd
Jim Fulton wrote:
I'm fine with change the storage server to pass the history size
argument as a keyword parameter.
Okay, but where is the Z309 equivalent of ZEOStorage308Adapter's history
method?
cheers,
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
11 matches
Mail list logo
