Tim Burke 4806434cb0 Move listing formatting out to proxy middleware ... Make some json -> (text, xml) stuff in a common module, reference that in account/container servers so we don't break existing clients (including out-of-date proxies), but have the proxy controllers always force a json listing. This simplifies operations on listings (such as the ones already happening in decrypter, or the ones planned for symlink and sharding) by only needing to consider a single response type. There is a downside of larger backend requests for text/plain listings, but it seems like a net win? Change-Id: Id3ce37aa0402e2d8dd5784ce329d7cb4fbaf700d		2017-09-15 06:38:26 +00:00
..
__init__.py	Initial commit of Swift code	2010-07-12 17:03:45 -05:00
auditor.py	Make log information format	2016-08-05 19:48:24 +08:00
backend.py	Add Timestamp.now() helper	2017-04-27 14:19:00 -07:00
reaper.py	Add Timestamp.now() helper	2017-04-27 14:19:00 -07:00
replicator.py	change default ports for servers	2016-04-29 14:47:38 -04:00
server.py	Move listing formatting out to proxy middleware	2017-09-15 06:38:26 +00:00
utils.py	Move listing formatting out to proxy middleware	2017-09-15 06:38:26 +00:00