== FROM THE DOCUMENTATION == "Alternatively, they can return a special constant, twisted.web.server.NOT_DONE_YET, which tells the web server not to close the connection; Doesn't this mean the web server automatically closes HTTP connections when request.close() is called? On Sun, 17 Oct 2004 23:30:43 -0400, James Y Knight <foom@fuhm.net> wrote:

On Oct 16, 2004, at 4:44 PM, Seun Osewa wrote:

...

Does Twisted.Web support persistent connections and pipelining?

Kindasorta. I believe it does HTTP 1.1 persistent connections.

...

how can I take advantage of this, if it does? And, if not, do you feel the interface is such that support for persistent connections can be transparently added?

It's all automatic, as far as it goes.

The new version of the http protocol for web2 supports it a lot better, and works with both HTTP 1.0 keepalive and HTTP 1.1 pipelining and persistent connections. Web2 is not ready for non-developmental use yet, however. The core HTTP protocol layer should be pretty stable at this point, but the layer above still needs work.

James

_______________________________________________ Twisted-web mailing list Twisted-web@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web

Seun Osewa <naijasms@gmail.com> writes:

== FROM THE DOCUMENTATION == "Alternatively, they can return a special constant, twisted.web.server.NOT_DONE_YET, which tells the web server not to close the connection;

Doesn't this mean the web server automatically closes HTTP connections when request.close() is called?

This has nothing to do with persistent connections. It just means that you have callbacks that must be triggered before the response will be finished.