We're in the final stages of preparing our app for production and looking for ways to improve performance. We have a number of data sources that typically have from zero to a few dozen records in any particular implementation so we've added cacheAllData="true" to these data sources.
Most of these data sources are simply used as the optionDataSource for SelectItems. The form that includes these SelectItems is created in a Window and when this Window is first shown we see a fetch request being sent to the server as expected. However, we continue to see fetch requests being sent to the server on subsequent draws of the form. We were expecting these to use the cached data set.
When the Window containing this form is closed we destroy it since the user may use other parts of the app and never return to that particular Window. Could this be causing the cached data to be dropped and then re-fetched when the form is drawn again? I didn't expect the cached data set to be affected by it's use in any particular form or other UI component.
Most of these data sources are simply used as the optionDataSource for SelectItems. The form that includes these SelectItems is created in a Window and when this Window is first shown we see a fetch request being sent to the server as expected. However, we continue to see fetch requests being sent to the server on subsequent draws of the form. We were expecting these to use the cached data set.
When the Window containing this form is closed we destroy it since the user may use other parts of the app and never return to that particular Window. Could this be causing the cached data to be dropped and then re-fetched when the form is drawn again? I didn't expect the cached data set to be affected by it's use in any particular form or other UI component.
Comment