swift/doc/saio
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
..
bin Bind SAIO services on different loopback addresses 2017-06-27 16:08:08 -04:00
rsyslog.d Use files in the source tree instead of cut/paste 2013-12-09 20:55:08 -05:00
swift Move listing formatting out to proxy middleware 2017-09-15 06:38:26 +00:00
rsyncd.conf Bind SAIO services on different loopback addresses 2017-06-27 16:08:08 -04:00