I'm pretty sure that the tempfile penalty is unrelated to the results
Paul sees in his tests, at least for smaller files.
If the content-length header indicates that the body of the item is
smaller than 128k, it does not appear to be spooled from a tempfile at
all. This also may be why there isn'
On Thu, 8 Apr 2004 [EMAIL PROTECTED] wrote:
> I'm working on a product which serves files from the filesystem. The
> data retrieval method is the usual:
>
> def pushData(self, f, outstream):
> finished = False
> while not finished:
> block = f.read(blocksize)
> if len(bloc
> In fact, Zope puts large files (the threshold is around 256K - 512K)
> into a temporary file before serving them, to free up application
> threads. It's a tremendous handicap.
I'm working on a product which serves files from the filesystem. The
data retrieval method is the usual:
def pushDat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I havn't received much feedback on the ZPT mailing list, so I
thought I'd bring it over here to a wider audience (thread is at
http://mail.zope.org/pipermail/zpt/2004-March/005218.html ).
Begin forwarded message:
From: Stuart Bishop <[EMAIL PROTECTED]>
On Thu, Apr 08, 2004 at 08:02:05PM -0400, Shane Hathaway wrote:
> On 04/08/04 12:16, Paul Winkler wrote:
> >On Wed, Mar 24, 2004 at 01:32:18PM -0500, Shane Hathaway wrote:
> >
> >>Jeremy has suggested that object pre-fetching could be added to ZODB.
> >
> >
> >This is much on my mind currently.
> >
On 04/08/04 12:16, Paul Winkler wrote:
On Wed, Mar 24, 2004 at 01:32:18PM -0500, Shane Hathaway wrote:
Jeremy has suggested that object pre-fetching could be added to ZODB.
This is much on my mind currently.
Any thoughts on what an API for pre-fetching might look like?
Well, thinking about it so
On Wed, Mar 24, 2004 at 01:32:18PM -0500, Shane Hathaway wrote:
> Jeremy has suggested that object pre-fetching could be added to ZODB.
This is much on my mind currently.
Any thoughts on what an API for pre-fetching might look like?
The use case that most concerns me is:
If you have an Image or F
On Wed, Mar 24, 2004 at 12:57:00PM -0500, Chris McDonough wrote:
>
> On Wed, 2004-03-24 at 09:28, Shane Hathaway wrote:
> > This sounds useful for serving content from the filesystem.
> >
> > However, I'm a little concerned about this because producers must not
> > read from the object database.
[EMAIL PROTECTED] wrote:
I've started looking at the ZODB and APE packages to try and get some
understanding of how the whole storage interaction works, but it'll take me
some time to figure it all out ... So I thought I'd get feedback on the idea
first ...
Sounds great! If I were you, I would sta
Erik A.Dahl wrote:
Thanks for the suggestion but no joy here. Here is the full trace...
Python 2.3.3 (#1, Jan 27 2004, 09:17:28)
[GCC 3.2 20020903 (Red Hat Linux 8.0 3.2-7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import Zope
>>> app = Zope.app()
>>
On Thursday 08 April 2004 10:00 am, Philipp von Weitershausen wrote:
> I would like to backport this patch (including tests) to Zope 2, since I
> need to i18n XML generated by ZPTs.
None here.
-Fred
--
Fred L. Drake, Jr.
PythonLabs at Zope Corporation
__
Gintautas Miliauskas wrote:
Update of /cvs-repository/Zope3/src/zope/tal
In directory cvs.zope.org:/tmp/cvs-serv27951/src/zope/tal
Modified Files:
talparser.py
Log Message:
Removed an assertion which disallows usage of Zope3 i18n in XML markup.
Added a few test cases which run the new code path.
Thanks for the suggestion but no joy here. Here is the full trace...
Python 2.3.3 (#1, Jan 27 2004, 09:17:28)
[GCC 3.2 20020903 (Red Hat Linux 8.0 3.2-7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import Zope
>>> app = Zope.app()
>>> app.testfolder
>>>
13 matches
Mail list logo
