[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zodb-dev
Subject:    Re: [ZODB-Dev] ZODB blob support.
From:       Jeremy Hylton <jhylton () gmail ! com>
Date:       2005-03-22 15:44:20
Message-ID: e8bf7a5305032207446ceebe07 () mail ! gmail ! com
[Download RAW message or body]

On Tue, 22 Mar 2005 10:35:25 -0500, Jim Fulton <jim@zope.com> wrote:
> Toby Dickenson wrote:
> > This approach suggests that you would need to transfer the *whole* *file* to
> > every client if even one byte of the blob was to change. Is there not a
> > requirement to handle this more efficiently?
> 
> Not that I'm aware of.

If modifying small chunks of a large blob is a common operation, I
suppose you would want to stick with the current Pdata scheme.  In
general, ZODB's design encourages you to organize an object using
composition of multiple persistent objects when you want to have
fine-grained control over update rates, caching, &c.  This sounds like
another instance of that principle.

Jeremy
_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev
[prev in list] [next in list] [prev in thread] [next in thread]