[Zope] audio order

Aaron aamehl at bezeqint.net
Sat May 22 16:50:12 EDT 2004

> *shrug* there are a lot of options there.
> It is now possible to "mount" multiple databases in one Zope instance.
> So all the audio files could go in a dedicated ZODB - something
> capable of scaling to many GB of data, so I'd probably
> choose DirectoryStorage.  Activity in this database wouldn't affect
> any other zope data.  And you could pack it however often you like.
So let me get this straight. I just setup directories and dump my files
in to them. 

I can have a zopedb for audio and and zopedb for notation, and another
zopedb for site related things?

> Re. some of the earlier comments:
> > On Fri, 2004-05-21 at 08:04, Aaron wrote:
> > > On Fri, 2004-05-21 at 03:02, Jerome R. Westrick wrote:
> > > > Hi Aaron...
> > > > 
> > > > I wouldn't place the songs in Zope...
> > > > Instead I would use LocalFS to get access to them...
> At one time I would have agreed, to keep the ZODB from getting
> unwieldy; but nowadays, unless I had another reason that I wanted
> the files easily accessible as plain files on the filesystem, I 
> would just use DirectoryStorage instead. It's robust, and given 
> an appropriate filesystem 

an appropriate filesystem??

> it can handle really massive amounts of data, 
> and it's easier to set up than fiddling around with LocalFS
> or ExternalFile or whatever.
> Download speed of blobs is still an issue. 
I doubt I will allow direct downloads and listening will be streaming.

Have you seen the audio products? In what way will they help me?

Is it good enough to make a folder and dump the audio in there or will
the audio products help me in some way?

> Note that the commonly deployed versions of LocalFS and many other 
> attempts at keeping Zope data on the filesystem actually perform MUCH
> worse than the normal ZODB-based File class.

I actually tried installing the patched LocalFS but didn't get to far
into it.
> I would handle the speed issue by throwing massive amounts of 
> disk caching at the problem. If the content is anonymously 
> downloadable I'd use Squid or apache + caching; if not, I'd use the 
> FileCacheManager that we hacked up at Pycon. 
> And if using ZEO, I'd use an enormous ZEO client cache.

Well I think the largest ogg file will be 9 megs. Certainly not 30- 50
I am not planning to run apache in addition to zope.  I haven't looked
at ZEO and I will do that soon I guess.

If anyone is willing/interested in giving some feedback about how to
best use zope for my project, My Wiki explains the project details and
design issues.

I would most welcome and comments, suggestions, etc.

Thanks again for the help.

I am as you can tell very new to Zope.


More information about the Zope mailing list