Hm. There is a lot in what you say. I was taking a look at http://web-sniffer.net/ to see what kind of headers are returning. In fact, it is just as you say: DreamObjects runs behind Apache and sets almost no headers, and this will for sure hurt caching performance. You’re right: this makes it bad for serving content publicly (unlike Amazon and other competing cloud storage services). But except for backups, what is DreamObjects worth for?
So this “request” is actually a bit more important than I thought, but probably also harder to implement than Cedric let us believe DH’s devs tend to amaze and surprise us, though, so it’s still early to say…
My current workaround is simply to place CloudFlare on front of everything stored by DreamObjects. CloudFlare (which is free to use) can selectively set the expire headers, so I added 8 days for the static content and 4 hours for the “mostly dynamic” content. This is really easy to set up!
Since CloudFlare caches everything anyway, it remains to be seen if DreamObjects is actually worth the trouble of configuring! I mean, I could set up the static content on a different subdomain name, and not even activate PHP on it, and do pretty much the same that I do with DreamObjects, e.g. push static content automatically from WP into a self-hosted, FTP-based domain. The only advantage of using DreamObjects is diminishing the traffic requests to the shared server I’m using…
Again, for a beta trial, the good thing is that it works and that there are workarounds But I would agree with you that maybe, just maybe, the 7 cents might be overpriced if we have far less control over how our content is stored and delivered… I’m sure DH will be looking very closely at this!
Ah, I posted the other message before reading this
Ipstenu, I guess that’s why some of your team are also busy working on a CDN solution: maybe you’re trying to “fix” the issue by pushing it into the CDN layer (which is pretty much what I’m doing right now with CloudFlare). The question then will be how much the CDN layer will additionally cost to us end-users