As FoxyCart users continue to grow and use FoxyCart on larger sites it's obviously increasing the load on our servers. Also, due to PCI compliance requirements, we are limited in certain ways, especially in regard to cloud hosting.
So, up to this point, the foxycart_includes.js files have dynamically served up the correct version of the file based on the store version (from the host in the request). This has worked, but:
-- Every request hits our servers, in the US, so it can be slower in Australia (notably) and elsewhere.
-- Every request pushes our servers a little more towards capacity, increasing our costs (and eventually our prices).
-- When our app servers go down, this creates problems if the files are included in the <head> of your sites. While we have very solid uptime, nobody's perfect.
In order to get around these issues we're looking at using a Content Delivery Network (CDN), which basically is a way to host files all around the world. This should _radically_ improve load times for those files as well as reduce our system load, allowing us to keep our costs as low as possible for you all.
The potential downside is that CDNs are "dumb", so if you're on v060, the CDN won't know. You'll have to enter a different file path depending on your store version. While that really shouldn't be an issue, it is a change.
We plan on maintaining the current functionality for existing store versions and for the near future, but we may eventually force all foxycart_includes.js and related CSS files to use the CDN. This should be a benefit to everybody, but we wanted to bring this up with the community to get feedback. If anybody has questions or concerns please let us know so we can address them and ensure things are communicated clearly.