||Thu, 03 July 2014 13:10
| Arnaud MERGEY
Registered: March 2010
Accessing to the same application but packaged with different RAP version, from the same browser instance, client crashes probably because rap-client.js and resources.js are cached.
For example, if you start a jetty with RAP 2.2 demo, and another jetty on the same machine with a different port and RAP 2.3 demo, from the same browser instance, it is not possible to switch from RAP 2.2. to RAP 2.3 demo, without having client error.
Port is not taken into consideration by browsers for caching, so it wrongly chaches rap-client.js for both
This could be solved by having rap version part of the url for ressources, /rwt-resources/2-3/rap-client.js for example
I agree it is a quite minor issue, but it can be ab bit anoying during an upgrade process, if you have users accessing your application, if you upgrade it with a new RAP version, all users that still have their browser instances kept alive between the 2 versions will face the error.
Is it seomthing that could deserve a bug ?
Powered by FUDForum
. Page generated in 0.11746 seconds