Chris Withers wrote at 2007-8-10 08:20 +0100:
>Martijn Pieters wrote:
>> On 8/9/07, Chris Withers <[EMAIL PROTECTED]> wrote:
>>> Indeed, but it's still a storage, there's no reason for it not to do
>>> conflict resolution itself. I thought it did ;-)
>>
>> It's not a storage at all.
>
>Really? I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> Martijn Pieters wrote:
>> On 8/9/07, Chris Withers <[EMAIL PROTECTED]> wrote:
>>> Indeed, but it's still a storage, there's no reason for it not to do
>>> conflict resolution itself. I thought it did ;-)
>> It's not a storage at
On 8/10/07, Chris Withers <[EMAIL PROTECTED]> wrote:
> > It's not a storage at all.
>
> Really? I'm pretty sure it implements the relevent storage interfaces
> otherwise it wouldn't slot in the place of FileStorage...
Just because it implements the interface doesn't make it a storage.
It's a stub,
Martijn Pieters wrote:
On 8/9/07, Chris Withers <[EMAIL PROTECTED]> wrote:
Indeed, but it's still a storage, there's no reason for it not to do
conflict resolution itself. I thought it did ;-)
It's not a storage at all.
Really? I'm pretty sure it implements the relevent storage interfaces
o
On 8/9/07, Chris Withers <[EMAIL PROTECTED]> wrote:
> Indeed, but it's still a storage, there's no reason for it not to do
> conflict resolution itself. I thought it did ;-)
It's not a storage at all. It's a stub for the actual storage which
lives in the server. That's a enormous difference. In fa
Martijn Pieters wrote:
That's what he's saying, yes. ClientStorage is a proxy for the
storages in the ZEO server, and it cannot know what features those
storages support. It therefore doesn't know anything about conflict
resolution.
Indeed, but it's still a storage, there's no reason for it not
On 8/9/07, Chris Withers <[EMAIL PROTECTED]> wrote:
> Hmmm, I guess I thought ClientStorage was conflict resolving, it sounds
> like you're saying it's not?
That's what he's saying, yes. ClientStorage is a proxy for the
storages in the ZEO server, and it cannot know what features those
storages su
Tres Seaver wrote:
If the conflict occurs between two threads on one app server, then I
would expect conflict resolution to happen on the app server and not the
storage...
I don't know how you calibrate your expectations, Chris, but conflict
resolution is a property of (some) *storages*; th
Tres Seaver schrieb:
I don't know how you calibrate your expectations, Chris, but conflict
resolution is a property of (some) *storages*; the connectoins in
application servers have nothing to do with it. For objects served from
a ZEO storage, conflict resolution is only possible if:
- The u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> Martijn Pieters wrote:
>> See the "Caveats and Dangers" section in:
>>
>>
>> http://svn.zope.org/ZODB/trunk/src/ZODB/ConflictResolution.txt?rev=77078&view=markup
>>
>> Conflict Resolution is a feature of a ZODB storage, and as
Martijn Pieters wrote:
On 8/7/07, Joachim Schmitz <[EMAIL PROTECTED]> wrote:
Yes ZEO is involved, but where do I specify a Products-directory in
etc/zeo.conf ?
You can't, AFAICT. ZEO servers only support one Products directory in
their INSTANCE_HOME, it appears.
'Products' is just like any o
11 matches
Mail list logo
