Apache Mod-Python - Commented: (MODPYTHON-238) req.connection.keepalive should

This is Interesting: Free IT Magazines  
Home > Archive > Apache Mod-Python > July 2007 > Commented: (MODPYTHON-238) req.connection.keepalive should





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Commented: (MODPYTHON-238) req.connection.keepalive should
Mike Looijmans (JIRA)

2007-07-09, 1:13 am


[ https://issues.apache.org/jira/brow...action_12511031 ]

Mike Looijmans commented on MODPYTHON-238:
------------------------------------------

If there is a separate req.chunked, I'd advise to keep them separated. It's perfectly valid to have
a chunked stream with a connection: close setting, and someone is bound to use that. For one thing,
it allows the client to reliably detect whether all the data has really been sent.

Having a side-effect like setting one disables the other is bound to surprise someone.

Mike Looijmans
Philips Natlab / Topic Automation






> req.connection.keepalive should be writable
> -------------------------------------------
>
> Key: MODPYTHON-238
> URL: https://issues.apache.org/jira/browse/MODPYTHON-238
> Project: mod_python
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.3.1
> Reporter: Graham Dumpleton
> Priority: Minor
>
> The attribute req.connection.keepalive should be writable. This would allow handlers to use:
> req.connection.keepalive = apache.AP_CONN_CLOSE
> Doing this before any data is written has the effect of disabling keepalive and also turning off chunked encoding for response content when no content length has been supplied.


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com