-----Original Message----- From: Doug McNaught [mailto:doug@mcnaught.org] Sent: Thursday, September 02, 1999 05:01 To: zope@zope.org Subject: Re: [Zope] ZODB size?
Michel Pelletier <michel@digicool.com> writes:
ZODB3 is limited to 18,446,744,073,709,551,616 objects. This should be adequate.
[...]
You will run into the 2GB ext2 file size limit long before you have any other problems.
So if I'm planning to serve out large data items (which, stored together, would push the ZODB over the 2GB limit) for download, I should create a mechanism to keep the actual data in the filesystem? Has anyone done this?
I created a basic mechanism that serves up all my large files. My requirements might be little different than yours. The main problem I was trying to solve was to have mirroring of large files at different locations. I wanted to use Zope and the Zope security model to restrict what could be downloaded. How I did this was to use a one-time token that last for about 10 mins. This token is created inside zope and used in a redirection to the approriate webserver. A simple python script authenticated the token and served up the file if the token checked out. This solution is one that is transparent to Zope but if anyone's interested I might be able to package it up somewhat.