Re: [Zope] unbuffered response.write through Apache 2.0 reverse proxy?

2006-02-21 Thread Chris Withers 

Christoph Berendes wrote:

so I've padded this with blanks to hit the buffer size. Klugey,but works.


Any reason why you don't just lower the buffer size?

Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk

___
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 )

Re: [Zope] unbuffered response.write through Apache 2.0 reverse proxy?

2006-02-20 Thread Christoph Berendes 

Chris McDonough wrote:

Apache does its own buffering IIRC.  Look for ProxyReceiveBufferSize/ 
ProxyIOBufferSize.



Thanks. AFAICT 
(http://httpd.apache.org/docs/2.0/mod/mod_proxy.html#proxyiobuffersize), 
though, the buffer size settings have to be fairly large (512 or more, 
or 0 for the system's default buffer size). I'm actually writing very 
short progress messages, e.g.


Parsing page 1...
Parsing page 2...

etc.

so I've padded this with blanks to hit the buffer size. Klugey,but works.




On Feb 18, 2006, at 3:59 AM, Christoph Berendes wrote:

To prevent browser timeout during a long running process, I've got  
the following code to work nicely,when the browser accesses Zope  
directly (e.g. http://myzope.net:8080/folder/client001/)


context.REQUEST.response.write(progressing...)
#do some stuff
context.REQUEST.response.write(further...)
#do some more stuff
context.REQUEST.response.write(done!)


However, when browser goes through the Apache reverse proxy, e.g.

VirtualHost *:80
ServerAlias   site1.foobar.com

  RewriteRule ^/(.*) \
 http://localhost:8080/VirtualHostBase/http/%{SERVER_NAME}:80/% 
1/site001/VirtualHostRoot/$1 [L,P]


I get all three writes (progressing..further...done!) at once, at  
the end of the processing.


I'm running Apache 2.0, Zope. 2.7.6, Plone 2.0.5 on Linux
From going through Apache docs and discussions (notably http:// 
www.gossamer-threads.com/lists/apache/dev/305433), it appears that  
this is an Apache 2.0 problem.


Is there any way to get the same behavior (unbuffered writes) even  
when I go through the Apache reverse proxy?


___
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 )

[Zope] unbuffered response.write through Apache 2.0 reverse proxy?

2006-02-18 Thread Christoph Berendes 
To prevent browser timeout during a long running process, I've got the 
following code to work nicely,when the browser accesses Zope directly 
(e.g. http://myzope.net:8080/folder/client001/)


context.REQUEST.response.write(progressing...)
#do some stuff
context.REQUEST.response.write(further...)
#do some more stuff
context.REQUEST.response.write(done!)


However, when browser goes through the Apache reverse proxy, e.g.

VirtualHost *:80
ServerAlias   site1.foobar.com

  RewriteRule ^/(.*) \
 
http://localhost:8080/VirtualHostBase/http/%{SERVER_NAME}:80/%1/site001/VirtualHostRoot/$1 
[L,P]


I get all three writes (progressing..further...done!) at once, at the 
end of the processing.


I'm running Apache 2.0, Zope. 2.7.6, Plone 2.0.5 on Linux
From going through Apache docs and discussions (notably 
http://www.gossamer-threads.com/lists/apache/dev/305433), it appears 
that this is an Apache 2.0 problem.


Is there any way to get the same behavior (unbuffered writes) even when 
I go through the Apache reverse proxy?


___
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 )

Re: [Zope] unbuffered response.write through Apache 2.0 reverse proxy?

2006-02-18 Thread Chris McDonough 
Apache does its own buffering IIRC.  Look for ProxyReceiveBufferSize/ 
ProxyIOBufferSize.



On Feb 18, 2006, at 3:59 AM, Christoph Berendes wrote:

To prevent browser timeout during a long running process, I've got  
the following code to work nicely,when the browser accesses Zope  
directly (e.g. http://myzope.net:8080/folder/client001/)


context.REQUEST.response.write(progressing...)
#do some stuff
context.REQUEST.response.write(further...)
#do some more stuff
context.REQUEST.response.write(done!)


However, when browser goes through the Apache reverse proxy, e.g.

VirtualHost *:80
ServerAlias   site1.foobar.com

  RewriteRule ^/(.*) \
 http://localhost:8080/VirtualHostBase/http/%{SERVER_NAME}:80/% 
1/site001/VirtualHostRoot/$1 [L,P]


I get all three writes (progressing..further...done!) at once, at  
the end of the processing.


I'm running Apache 2.0, Zope. 2.7.6, Plone 2.0.5 on Linux
From going through Apache docs and discussions (notably http:// 
www.gossamer-threads.com/lists/apache/dev/305433), it appears that  
this is an Apache 2.0 problem.


Is there any way to get the same behavior (unbuffered writes) even  
when I go through the Apache reverse proxy?


___
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 )