See also http://www.zope.org/Wikis/DevSite/Proposals/
FasterStaticContentServing
On Sep 29, 2006, at 10:48 AM, Stefan H. Holek wrote:
The point of stream iterators is not the chunk size, but that they
are handed to Medusa (ZServer) right away. As a result the Zope
thread is immediately freed to serve new requests, while ZServer
takes care of streaming the data to the client.
Stefan
On 29. Sep 2006, at 15:14, Pascal Peregrina wrote:
Hi,
I would like to know what is the use of implementing the
Zpublisher.Iterators.IStreamIterator on the object returned as the
body of a
HTTP response.
As far as I could read the Zope code (Zserver, etc), this will
make the
response data to be sent 64k at a time.
So will this improve performance/concurrency in any way for >64k
data HTTP
responses?
--
Anything that, in happening, causes itself to happen again,
happens again. --Douglas Adams
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
