swift/swift
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
..
account Move listing formatting out to proxy middleware 2017-09-15 06:38:26 +00:00
cli Test placeholder for dispersion_report module 2017-09-13 16:49:00 -06:00
common Move listing formatting out to proxy middleware 2017-09-15 06:38:26 +00:00
container Move listing formatting out to proxy middleware 2017-09-15 06:38:26 +00:00
locale Imported Translations from Zanata 2017-08-25 07:41:28 +00:00
obj Always require device dir for containers 2017-09-01 10:32:12 -07:00
proxy Move listing formatting out to proxy middleware 2017-09-15 06:38:26 +00:00
__init__.py Make pbr a build-time only dependency 2013-10-29 12:29:49 -07:00