bf3261f86dd2d0eb9a51b2b570ad8113f7b0276f
FAQ/Questions/Caching.md
| ... | ... | @@ -34,6 +34,14 @@ The ``FusionCache.RefreshAllCachedReports`` method can be called to update the c |
| 34 | 34 | |
| 35 | 35 | The ``FusionCache.RefreshAllCachedDashboards method will update the cache of XML dashboards, but not reports, based on whether the time period specified in the [[DataCacheInterval|/API/CodeSamples/DataCacheInterval]] setting has elapsed since the last time the dashboard was cached. This can be called based on your unique business logic. |
| 36 | 36 | |
| 37 | +###StaticSharedStorage |
|
| 38 | + |
|
| 39 | +The StaticSharedStorage class is used to implement a completely static memory mode for the entire application. This must be set before any calls to the Izenda API if it is to be used. This means that it must come before even the license key declaration. Otherwise, Izenda will automatically store much of its configuration data in Session. Here is how to initialize the class: |
|
| 40 | + |
|
| 41 | +```csharp |
|
| 42 | +StaticSharedStorage.Activate(true); |
|
| 43 | +``` |
|
| 44 | + |
|
| 37 | 45 | ###Limitations |
| 38 | 46 | |
| 39 | 47 | 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 |