Just a heads up, for people who're not sure:
None of the Linux binary downloads of Zope I've tested (including
2.5.1b1) are built with Large File Support in python. Also unstable
Debian's python is without Large File Support, same thing with Mandrake
8.1.
If you want to check for yourself your
On Tue, 24 Oct 2000 20:31:52 +0200, [EMAIL PROTECTED] wrote:
If the Zope object knows how to produce the data themselves, they
could push producer(s) directly to the channel. I added a single
check in ZServer.HTTPResponse(256) where a temporary file is only
created
How does this differ from Local FS?
cheers,
Chris
[EMAIL PROTECTED] wrote:
I have been building an "ExternalFile" class which stores the body of
the file in an external file, mirroring the Zope path/hierarchy. This
will allow easy integration with servers that can mount the external
There is not much difference between the ExternalFile class I'm working
with and the File objects produced by LocalFS except External Files can
be put anywhere in the Zope hierarchy and LocalFS files need to be under
a LocalFS. Each approach has its pros and cons.
This proposal mostly deals
I should also note that if you create a producer, you will have to
override the __len__ method to return the entire length of the data.
This is because RESPONSE.write doesn't allow you to set the
length of a
write and there code during output that checks the size of the written
object.
