Nick Raptis 202ede3c54 Accurately timestamp start of request ... When building a request from a stream, try to get an accurate start timestamp from the Reader. This was already in the code and also used when building response objects, but was ommited in commit ddf458b330 Without his logic and when the client is reusing a connection to send requests, the timestamp_start of subsequent requests is early and equal to when the connection started read blocking		2015-05-08 10:58:05 +03:00
..
console	Adapt to new Pathoc API - silence output to stdout.	2015-05-02 16:46:15 +12:00
contrib
onboarding	onboarding app: serve certs inline to unbreak firefox	2015-03-19 16:29:05 +01:00
platform	+ Use sys.platform.startswith("freebsd") instead of matching just freebsd10.	2015-04-27 02:31:58 +01:00
protocol	Accurately timestamp start of request	2015-05-08 10:58:05 +03:00
proxy	adjust to changed netlib api	2015-03-07 01:39:01 +01:00
web	web: try harder to fix editor	2015-05-01 20:45:31 +02:00
webfonts
__init__.py
cmdline.py	console: add a -l flag to set the limit on startup	2015-04-15 12:56:43 +12:00
controller.py
dump.py	pretty_size now lives in netlib.utils	2015-04-30 12:18:01 +12:00
encoding.py
filt.py
flow.py	Adjust for ODict interface change	2015-04-15 10:29:57 +12:00
main.py	console: add a -l flag to set the limit on startup	2015-04-15 12:56:43 +12:00
script.py	fix #110	2015-02-07 16:37:59 +01:00
stateobject.py
tnetstring.py
utils.py	pretty_size now lives in netlib.utils	2015-04-30 12:18:01 +12:00
version.py