Hi Steve,
Steve Spicklemire writes:
Hmm.. I just tried this with my highly experimental product
(LocalProc 0.0.1) and I didn't observe the same effect that you did
behind my Proxy Server.
Whether you see this effect or not depends on the HTTP
processing in the chain between your
He reported, that this response page is build only
half, then stops, to be completed only half a minute later,
Depending on how long the page is I never see the bottom. When I use the products
page I have to refresh 2-3 times to see the bottom part.
This is thru a proxy only.
How to fix the problem:
There should be a (file) control "CloseOnExec", that tells
Unix to automatically close the file like object upon
an exec.
ZServer should probably use it on each of its sockets.
I can not see a serious application that should have
Hi Deiter,
Hmm.. I just tried this with my highly experimental product
(LocalProc 0.0.1) and I didn't observe the same effect that you did
behind my Proxy Server. (I normally run with Rewrite... but when I got
your note I tried ProxyPass and it worked on the first try.)
(Good howto Anser!
He reported, that this response page is build only
half, then stops, to be completed only half a minute later,
Depending on how long the page is I never see the bottom. When I use the products
page I have to refresh 2-3 times to see the bottom part.
This is thru a proxy only.
How to fix the problem:
There should be a (file) control "CloseOnExec", that tells
Unix to automatically close the file like object upon
an exec.
ZServer should probably use it on each of its sockets.
I can not see a serious application that should have
Today was again a hard Zope day.
Did you ever hear, that usually (i.e. if you do not do special
things) Zope renders a complete page before it starts
sending the result back to the client.
This implies that you should never see only half of a page.
I heard it and I saw the code that does it.
