It would be nice if we could add a CNAME to that, e.g. myobjects.mydomainname.tld (if you do that, DreamObjects will complain about a Bad Request), like Amazon S3 does.
It’s not just a question of “having nice names”. It has two advantages:
- Google’s ranking algorithm will prefer things that come from the same domain, specially if there are a lot of “things” (why, I don’t know).
- More important than that: DreamHost is a CloudFlare partner. If static content is served from the same domain name, then CloudFlare can act as a CDN for DreamHost objects. Why is this important? Because CloudFlare is able to distribute content among their 14 data servers, providing better service (shorter round-trip time in delivering content) to the whole world. Of course, if your DreamObjects-enabled web app is targeted only at people living in cities near DH’s own data centers, this will be mostly irrelevant (even though CloudFlare will add lots of additional functionality, like dealing with spammers/scammers/security breaches, etc.). For the rest of us, though, having CloudFlare on top of DreamObjects is a cool extra bonus (for free).
Is this somehow also on DH’s list of upcoming features when DreamObjects gets out of Beta?