You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no support to configure multiple cloudfront distributions for a given bucket. But I see no reason why this would be needed. Comment and vote for this if you do not agree.
The text was updated successfully, but these errors were encountered:
From: James Murty <james@misterm.org>
Subject: [JetS3t Users] Re: Amazon CloudFront support
Date: 26. November 2008 00:26:12 MEZ
To: jets3t-users@googlegroups.com
Reply-To: jets3t-users@googlegroups.com
I suppose you might gain an advantage having multiple distributions for a
single bucket if you serve pages with many components to web browsers that
limit the number of simultaneous connections per site. I believe that many
browsers do this, some with as few as 4 connections per site. If you serve a
page with many images for example, the connection restrictions may prevent
the browser from using all the available bandwidth to load the page.
People sometimes use multiple CNAMEs to work around per-site restrictions,
and you can use this approach with CloudFront's CNAME support as well, but
by setting up multiple distributions you could achieve the same thing
without having to set up the CNAMEs or worry about DNS stuff at all.
There is currently no support to configure multiple cloudfront distributions for a given bucket. But I see no reason why this would be needed. Comment and vote for this if you do not agree.
The text was updated successfully, but these errors were encountered: