litesoft
@ HEAD
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 |
<!DOCTYPE html> <html><head><title>Caching Solution w/ URL Versioning and Cache Control</title></head> <body> <center> <h1>Caching Solution w/ URL Versioning and Cache Control</h1> </center> <p> Premise: <p> If EVERY THING was cached forever EXCEPT the bootstrap.js, and each version of the app included the version number in the url, then older version's bootstrap.js could client-side forward the full URL to the current version.<p> This would facilitate old "deep link" bookmarks still working. <p> Example / Demo: <p> <ul> If the bookmarked URL were: <p> <ul><a href="http://localhost:8080/CSidea/v1#DeepLinkStuff" target="_blank">http://localhost:8080/CSidea/v1#DeepLinkStuff</a></ul> <p> but the current version was "v2", then the "v1" bootstrap.js would forward to: <p> <ul><a href="http://localhost:8080/CSidea/v2#DeepLinkStuff" target="_blank">http://localhost:8080/CSidea/v2#DeepLinkStuff</a></ul> <p> In addition new customers w/o a bookmark could use the standard launch page:<p> <ul><a href="http://localhost:8080/CSidea" target="_blank">http://localhost:8080/CSidea</a></ul> </ul> <p> For this to be a reasonable approach, it must be easy to generate new versions, and since old "forwarding" versions will need to stick around for some time, each old version should take up the least possible space. </body> </html> |