On 5/29/05, Shane Hathaway <[EMAIL PROTECTED]> wrote:
> > Would a multi thread ZEO server improve anything here? Especially
> > with concurrent access?
>
> It's possible. Although ZEO talks over the network using async sockets,
> it reads files synchronously, so I suspect it will frequently sit a
Tino Wildenhain wrote:
> Am Sonntag, den 29.05.2005, 09:51 +0200 schrieb Andreas Jung:
>>The Pdata approach in general is not bad. I have implemented a CVS-like file
>>repository lately where we store binary content using a pdata like
>>structure.
>>Our largest files are around (100MB) and the per
Am Sonntag, den 29.05.2005, 09:51 +0200 schrieb Andreas Jung:
>
> --On 29. Mai 2005 11:29:06 +0200 Christian Theune <[EMAIL PROTECTED]> wrote:
>
> > Am Samstag, den 21.05.2005, 17:38 +0200 schrieb Christian Heimes:
> >> Grab the Zope2 sources and read lib/python/OFS/Image.py. Zope's
> >> OFS.Imag
--On 29. Mai 2005 11:29:06 +0200 Christian Theune <[EMAIL PROTECTED]> wrote:
Am Samstag, den 21.05.2005, 17:38 +0200 schrieb Christian Heimes:
Grab the Zope2 sources and read lib/python/OFS/Image.py. Zope's
OFS.Image.Image class (and also Zope3's implementation) is using a so
called possible
Am Samstag, den 21.05.2005, 17:38 +0200 schrieb Christian Heimes:
> Grab the Zope2 sources and read lib/python/OFS/Image.py. Zope's
> OFS.Image.Image class (and also Zope3's implementation) is using a so
> called possible large data class (Pdata) that is a subclass of Persistent.
>
> Pdata is us
