Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use vhosted buckets by default, if available
- We still use the s3.amazonaws.com hostname for the underlying requests, but for best performance, we want to _connect_ to the vhosted bucket if it's possible (e.g., valid dns name). - We do this by actually looking up DNS when you create a new bucket object without a conn (and plugging in a modified dialer). Rationale: bucketname.s3.amazonaws.com is geographically cnamed by amazon down through the appropriate load-balancers and caches to ensure the best performance of your bulk traffic. It also ensures you're pointed to the best /frontend/ to have the fewest problems with S3's 'eventual consistency' model. Unanswered Questions: - Does Go DNS cache dns results? If so, does it obey TTL's? - What is the meaning of life?
- Loading branch information
James D. Nurmi
committed
Jun 22, 2011
1 parent
75b3ecb
commit 82e7828
Showing
2 changed files
with
31 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters