Add compression options to object PUTs
Another idea from irc:jeremyb is to offer compression options during object GETs.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
While it makes more sense to require client-side compression for more public clusters, private cluster owners might want to trade their server-side CPU for server-side disk usage by compressing objects either transparently or on client demand.
Client-demand would be like doing a normal PUT but with an extra header to indicate compression is desired. Options to serve the compressed object or uncompressed object on GETs could be provided.
Transparent compression could be performed on the server-side automatically compressing all object PUTs and serving all objects uncompressed. The client would never know the difference.
Gerrit topic: https:/
Addressed by: https:/
Add server side object compression support
