Jim Fulton wrote:
I could certainly find evidence that you tried, but the implementation was
actually buffering data in a string buffer until the request was finished.
This was the case at least as early as spring of 2004.
Even with more than 105 bytes output over a slow connection?
Shane Hathaway wrote:
Jim Fulton wrote:
I could certainly find evidence that you tried, but the implementation
was
actually buffering data in a string buffer until the request was
finished.
This was the case at least as early as spring of 2004.
Even with more than 105 bytes output
Jim Fulton wrote:
Shane Hathaway wrote:
A pull strategy will be efficient for a lot more people.
I don't know what you mean by this.
I mean that the new strategy of sending open files to the publisher,
which I call a pull strategy, will work better than pushing to temporary
files. Which
Philipp von Weitershausen wrote:
page 204, Example 12.24, line 17: Using the ``write()`` method of
HTTP-based responses does not provide a performance advantage in
Zope X3 3.0 and 3.1 and is not supported anymore in Zope 3.2 and
higher.
I would like to point out that response.write()
Philipp von Weitershausen wrote:
Shane Hathaway wrote:
So I fully agree that the original write() should go (in fact I suppose
it's gone already), but to say there was no performance advantage is
imprecise. I spent a fair amount of time making write() fast, with some
success.
Interesting.
Shane Hathaway wrote:
Philipp von Weitershausen wrote:
So using write() once doesn't at all seem like an advantage over simply
returning the data...
The interesting part is behind the scenes. If the response is large
enough (it's an adjustable threshold), the response transparently gets
Shane Hathaway wrote:
Shane Hathaway wrote:
Philipp von Weitershausen wrote:
So using write() once doesn't at all seem like an advantage over simply
returning the data...
The interesting part is behind the scenes. If the response is large
enough (it's an adjustable threshold), the
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
When we refactored the Zope 3 pubisher to work more closely with WSGI,
we decided to remove the response.write method. We should have written
a proposal for this, but we failed to do so. Over the last few
