One reason these things don't support append is at some point they need to choose the "version" of the object. Usually this is done when an object upload has completed.
If they allow arbitrary appends to objects, then they would have a hard time assigning any type of ordering to them, as the concept of an object being "complete" would be thrown out the window.
(EDIT: and what does it mean to have a GET on an object, if you don't know the latest version to return?)
I think something like this could be implemented, but it would probably be an entirely different product that supported some specific traditional file operations (rename, ftruncate, link, etc) but had different scaling properties.
One reason these things don't support append is at some point they need to choose the "version" of the object. Usually this is done when an object upload has completed.
If they allow arbitrary appends to objects, then they would have a hard time assigning any type of ordering to them, as the concept of an object being "complete" would be thrown out the window.
(EDIT: and what does it mean to have a GET on an object, if you don't know the latest version to return?)
I think something like this could be implemented, but it would probably be an entirely different product that supported some specific traditional file operations (rename, ftruncate, link, etc) but had different scaling properties.