-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stephan Richter wrote:
> On Thursday 14 April 2005 13:43, Sidnei da Silva wrote:
> 
>>On Thu, Apr 14, 2005 at 01:22:53PM -0400, Stephan Richter wrote:
>>| On Thursday 14 April 2005 13:00, Florent Guillaume wrote:
>>| > > +    def __init__(self, stream):
>>| > > +        self.stream = stream
>>| > > +        self.cacheStream = cStringIO.StringIO()
>>| >
>>| > Won't a memory cache be a problem for multi-megabytes POSTs ?
>>|
>>| Maybe, but we have no choice here. The only other option is to make it a
>>| temporary file.
>>
>>Maybe!?! Please, give it some thought. It has caused lots of pain in
>>Zope 2, which just recently got fixed. That means a 'temp hack' can
>>live as much as 8 (?) years.
> 
> 
> Any constructive input? Will a temporary file be better? Will it work easily
> cross-platform? How was this solved in Zope 2?

Sidnei is correct that a RAM cache is not appropriate here;  a tempfile
(but only one!) is the only sane route.  Note that Python's CGI module
*also* creates tempfiles, which can lead to a copy (it does in Zope2):


http://cvs.zope.org/Zope/lib/python/ZServer/Attic/HTTPServer.py?hideattic=0&sortby=date


Tres.
- --
===============================================================
Tres Seaver                                [EMAIL PROTECTED]
Zope Corporation      "Zope Dealers"       http://www.zope.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCXrTbGqWXf00rNCgRAinfAJ9NY/OGWNY/2KTOyJ5aLwSA6yDnYwCfXfp+
eeKHGt+EkYwB4/w/bNOqm7c=
=I8Qe
-----END PGP SIGNATURE-----

_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to