raymor

Expect problems. There is a right way to do a CDN. It was documented in the HTTP standard and Google and others have done it on the origin side for years. AOL and other ISPs have been doing it for years on the ISP side. Unfortunately, when "CDN" became a buzzword a lot of companies developed CDNs without paying any attention at all to how they need to be set up in order to work right. Some of the larger hosting companies have CDNs full of HUGE mistakes. Before CDN was a buzzword it was called a reverse proxy network. Sometimes I wonder if some of the people setting them up now even know that what they are setting up is called a reverse proxy. Based on the cluelessness of some of the CDN designs, it looks like the designers just dreamed up their own ideas without knowing anything about what's known to work, what's known to not work, and what is required by the standards.

All that say - expect problems. After you work around the problems, expect that a few months later more subtle problems will be revealed.

__________________
For historical display only. This information is not current:
support@bettercgi.com ICQ 7208627
Strongbox - The next generation in site security
Throttlebox - The next generation in bandwidth control
Clonebox - Backup and disaster recovery on steroids