Thanks I'll have a look at that.
Anyway, memory is cheap :)
Memory is cheap but 20 clients x 20 meg download goes through your memory pretty quick... Cheers. -- Andy McKay. ----- Original Message ----- From: "marc lindahl" <marc@bowery.com> To: "Andy McKay" <andym@activestate.com> Cc: <zope@zope.org> Sent: Wednesday, May 02, 2001 1:49 PM Subject: Re: [Zope] Announce - Audio Product
I don't think it ever did this. From looking at File, which Image and Audio are both based on, it has this data type called Pdata(). It uses this whenever the data size is larger than 2^16 (an arbitrary number buried in the file). What that does is, it chops the file into chunks (of, I think, 2^16), and builds a linked list of them. Then when it stores or retrieves the file, it only has one chunk in memory at a time. Same when it renders it, it writes it out one chunk at a time. Take a look in OFS/Image.py at the bottom of the file.
Anyway, memory is cheap :)
From: "Andy McKay" <andym@ActiveState.com>
My main problem is that serving back a large file through Zope sucks as it puts the whole thing in memory. Has this been solved since last time I looked?
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )