FWIW, I came across a CDN fallback to local version method, that works...
Code: Select all
http://developer.yahoo.com/performance/ ... #js_bottom
I have been staying out of the CDN debate until now but I do offer the following considerations:
1. We must include jquery locally. This is needed to support disconnected (from the internet) operation.
2. Because of #1 the decision is between having a local copy only or having local copy + CDN. Since the local copy is already essentially implemented, whether CDN will be an option or not depends on someone implementing it. In my opinion having CDN support is not a requirement for merging jquery into develop.
How to actually implement CDN seems to be tricky. I am not a big fan of telling admins to edit the code if they want a CDN. We are trying to move away from modifying core code and this in a step in the opposite direction. Perhaps we can simply provide a config variable (hidden or visible) where an admin can put the full path to where they want to get jquery from. This will let admin specify whichever version they want and whichever CDN they want, freeing us from having to maintain a list of CDNs as well as worrying about those CDNs not carrying versions that we use.