javascript - Locally serving filepicker.io JS -


we use require.js handle javascript module loading. how source @ http://api.filepicker.io/v1/filepicker.js updated? safe (as in won't cause our app break when make changes) download , serve locally via such module loader?

i assume because of versioning in directory on updating api you'll update directory.

overall, recommend against storing filepicker.js locally.

while try not change javascript (for caching purposes, one), push out changes fix issues found or add new features. occasionally, things don't affect external api, change way library communicates our servers - in these cases, if using copy stored locally, implementation no longer work.

with regard "v1" versioning, version number of api (rather js include), distinguish v0 api deprecated in december 2012.


Comments

Popular posts from this blog

linux - Does gcc have any options to add version info in ELF binary file? -

android - send complex objects as post php java -

charts - What graph/dashboard product is facebook using in Dashboard: PUE & WUE -