The timeframe is quite irregular (sometimes a few minutes - sometimes several hours), but if a user is logged into our smartGWT application over a longer period of time, sooner or later the UI-components degenerate, because previously unused images are not loaded.
This happens for both smartGWT skin images and our own images (and actually also css files). It's particular apparent with the mouse over images of the smartGWT skins...after a while these are not available to the browser it seems.
We suspect the session timeouts and lazy loading of additional images are no longer possible. But this doesn't correspond with the fact that the user may still access other new tabs or other functionality...all that's missing are the images!! Or maybe the caching settings in the browser, app server or http headers are responsible?!?!
We are currently running the application on a Tomcat6 with a Spring 3.0 backend on a Windows 2003 server and the behaviour is the same in both chrome, ie, firefox.
This happens for both smartGWT skin images and our own images (and actually also css files). It's particular apparent with the mouse over images of the smartGWT skins...after a while these are not available to the browser it seems.
We suspect the session timeouts and lazy loading of additional images are no longer possible. But this doesn't correspond with the fact that the user may still access other new tabs or other functionality...all that's missing are the images!! Or maybe the caching settings in the browser, app server or http headers are responsible?!?!
We are currently running the application on a Tomcat6 with a Spring 3.0 backend on a Windows 2003 server and the behaviour is the same in both chrome, ie, firefox.
Comment