Samuel Merritt 6acea29fa6 Move all DLO functionality to middleware ... This is for the same reason that SLO got pulled into middleware, which includes stuff like automatic retry of GETs on broken connection and the multi-ring storage policy stuff. The proxy will automatically insert the dlo middleware at an appropriate place in the pipeline the same way it does with the gatekeeper middleware. Clusters will still support DLOs after upgrade even with an old config file that doesn't mention dlo at all. Includes support for reading config values from the proxy server's config section so that upgraded clusters continue to work as before. Bonus fix: resolve 'after' vs. 'after_fn' in proxy's required filters list. Having two was confusing, so I kept the more-general one. DocImpact blueprint multi-ring-large-objects Change-Id: Ib3b3830c246816dd549fc74be98b4bc651e7bace		2014-02-03 18:29:48 -08:00
..
account	Use a tempfile.mkdtemp() based temporary directory	2014-01-19 16:29:45 -05:00
common	Move all DLO functionality to middleware	2014-02-03 18:29:48 -08:00
container	Container Sync: Simple HTTP Proxy load balancing	2014-01-23 01:16:05 +00:00
obj	Move all DLO functionality to middleware	2014-02-03 18:29:48 -08:00
proxy	Move all DLO functionality to middleware	2014-02-03 18:29:48 -08:00
test_locale	Move test.unit.locale out of gettext's way	2014-01-24 01:24:08 -08:00
__init__.py	Merge "Fix bug in obj updater run_once()."	2013-11-27 17:52:49 +00:00