[imported_silkroad]

AWS CF charges in many ways ways:

(1) Uploading files to S3 storage (bandwidth).
(2) Pulling from CF to S3 (bandwidth and per request) and
(3) Pulling from the CF CDN (per request and bandwidth).

There are probally more charges. AWS CF/S3 is not cheap.

I wonder if there is a price comparision on the net?

--------------- Added [DATE]1251143701[/DATE] at [TIME]1251143701[/TIME] ---------------

I was checking.... I think I'm going to give SimpleCDN a try and compare with Cloudfront...

Thanks for the tip about "Mirror Bucket"

--------------- Added [DATE]1251149179[/DATE] at [TIME]1251149179[/TIME] ---------------

Originally Posted by RedWingFan

On our server, avatars are in /forums/images/customavatars, so they are served by the CDN thanks to my directing the entire /images directory to SimpleCDN. The difference, though, is that SimpleCDN uses a "mirror" type of delivery where, if an image is requested from the CDN, and it is not cached there, it will grab it from the server. That is why I can safely push the avatars to visitors via SimpleCDN.

OK, I see, you are 301'ing your entire image directory :-)

That explains how you get the customavatars in the CDN. I searched the templates and the phases and could never find how to set a CDN URL for avatars (and a few other hard coded image paths).

I don't understand why Jelsoft hard coded the customavatar domain as the forum domain and made it necessary to 301 those over to a CDN