8260f8ef7b3a10103ab933b7bb0ec3061406aa58
FAQ/Questions/Caching.md
| ... | ... | @@ -72,4 +72,7 @@ StaticSharedStorage.Activate(true); |
| 72 | 72 | |
| 73 | 73 | ###Limitations |
| 74 | 74 | |
| 75 | -Izenda Reports is a web application. Therefore, caching is susceptible to the client state. For example, do not have Izenda Reports running in separate windows or tabs of Internet Explorer. Otherwise, you could get the following behavior: by loading a report in one window and then loading a different report in another window, you may have unknowingly cached the second report, overriding the first. To properly enforce caching, only have a single instance of Izenda Reports running at a time per browser session. If you do open other browser windows and create/modify reports in that window, be sure you do not go back to the previous tab to continue modifying reports. Otherwise, you may see the newly cached report in your viewer instead of the one you were expecting to see. |
|
| ... | ... | \ No newline at end of file |
| 0 | +Izenda Reports is a web application. Therefore, caching is susceptible to the client state. For example, do not have Izenda Reports running in separate windows or tabs of Internet Explorer. Otherwise, you could get the following behavior: by loading a report in one window and then loading a different report in another window, you may have unknowingly cached the second report, overriding the first. To properly enforce caching, only have a single instance of Izenda Reports running at a time per browser session. If you do open other browser windows and create/modify reports in that window, be sure you do not go back to the previous tab to continue modifying reports. Otherwise, you may see the newly cached report in your viewer instead of the one you were expecting to see. |
|
| 1 | + |
|
| 2 | +###More Information |
|
| 3 | +[[Izenda Caching Lifecycle|http://wiki.izenda.us/FAQ/Izenda Caching Lifecycle]] |
|
| ... | ... | \ No newline at end of file |