Most of them work off the pull method. Basically you set a URL in the CDN's control panel that is the source. If the file is not in the CDN, then it will pull from that source url, so:

main site: http://www.example.com (this would be your source) cdn: http://cdn.example.com

There are also push CDNs out there, which you got to actually send the file to, but those are a lot harder to set up.

Jamie Holly http://www.intoxination.net http://www.hollyit.net

On 6/16/2011 11:22 AM, Ms. Nancy Wichmann wrote:

Thanks, Earnie.

Yes, I am aware of how to enable compression and its benefits (particularly regarding IE's 32 file limit). Clearly the site has not enabled those options.

I am not, however, fully versed in CDNs. I know they are theoretically dispersed and allegedly faster (although my anecdotal experience is different). I don't, for example, know how the data is supposed to be propagated into the CDN. Do most just pick up files as they are created? That would be fabulous and allow me to easily test the speed issue - assuming I get the job. If I have to physically push the file out, that makes it a bit more difficult.

/*Nancy*/

Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.

------------------------------------------------------------------------
*From:* Earnie Boyd

> First question: would it be faster to use the compressed CSS
file right from the site?

The performance maintenance page allows the CSS and JS to be
compressed
into a single file if these performance check boxes are enabled.

> Second question is there a way to consolidate those files (like
a compressed file) onto a CDN, if they believe strongly in CDNs?

Hmm, if the performance maintenance page options are enabled, I don't
know that it matters.  How is the CDN data replicated?  If the files
accessed by the web page are replicated across all hosts in the
CDN then
the single file should also be.