> > > Perhaps the AssetDispatcher could check the requested version number and if > it doesn't match the app version, send a 302 redirect to the "correct" URL? > /assets/1.3/ctx/script.js --> /assets/1.2/ctx/script.js > > Or perhaps it should only deliver the asset if the requested version os > older than or equal to the app version? > Determining "older" and "newer" would however assume people name their > application versions in a certain way.
It is exactly what I did in my application. I have overridden AssetsDispatcher service with my copy based on original one, that differs only in handling missing resources: if resource actually exists but just version numbers differ, my dispatcher just sends redirect response with a correct path. As a side note, I observed in that - at least in my case - typically a favicon was a typical asset requested with wrong version number, probably from bookmarks. Regards, Cezary
