Future features

Future features

Object Storage Swift API related functionality

• chunking -> http://docs.openstack.org/api/openstack-object-storage/1.0/content/chunked-transfer-encoding.html
• CORS -> http://docs.openstack.org/api/openstack-object-storage/1.0/content/assigning-cors-headers-to-requests.html
• Content encoding -> http://docs.openstack.org/api/openstack-object-storage/1.0/content/enabling-file-compression-with-content-encoding-header.html
• Content disposition (ie, bypassing content handling in the browser, and forcing file save) -> http://docs.openstack.org/api/openstack-object-storage/1.0/content/enabling-browser-bypass-with-content-disposition-header.html
• Versioning -> http://docs.openstack.org/api/openstack-object-storage/1.0/content/Object_Versioning-e1e3230.html, better yet Folsom's object versioning -> http://docs.openstack.org/developer/swift/overview_object_versioning.html
• Fine-grained authorization on containers -> http://docs.openstack.org/api/openstack-object-storage/1.0/content/special-metadata-acls.html
• Pseudo-hierarchies (to emulate directory structures) -> specifically, example 4.36/4.37 (path and delimiter) in http://docs.openstack.org/api/openstack-object-storage/1.0/content/folders-directories.html
• Automatically apply Swift convention for large objects, which is to store segmented objects separate from the manifests into a "_segments"-postfixed container: http://docs.openstack.org/developer/swift/overview_large_objects.html

Wishlist for JOSS separate from Object Storage functionality

• Content-sniffing; make content-sniffing (as opposed to file extension matching) a part of JOSS
• Persistable in-memory Object Store; useful if a server is running on in-memory object store and wants to persist its state after a server restart
• Method for asking whether an object's metadata has been read