Expires Headers in Mezeo

[clintv]

Currently, S3 doesn't have a good solution for pushing content that should be cached for a time period by the user.  The main issue is that the expires header is static so when you push it to the cloud it expires on the day you say it does.  The optimal thing to do would be to have a way to say cache for X amount of time.  So if I say cache this file for 7 days, then pull it off the server next week, it would set headers saying it expires that time + 7 days.

I was curious if Mezeo has something that solves this problem developers run into when placing things like site images into the cloud.

[Travis McLane]

I am not sure I completely understand your question.
You wish to have the ability to remove an item from the cloud but still have it accessible for some time period following the removal?

Removing it from the cloud would of course make the item inaccessible through any of the available apis.

Would you mind explaining this further and provide a more concrete use case?