we are using client side state saving. On Sat, Aug 25, 2012 at 11:21 PM, parthiv pradhan <[email protected] > wrote:
> Hi All, > > In our application we have extensively used trh:tablelayout and this is > causing huge memory problem for us. In heap dump we found that the view > state is almost taking up around 1.5 MB of memory per session. It is too > late considering the deliverable to make the UI changes. In this event we > want to override the StateManagerImpl class to save the view and state to a > Cache instead of the session. so while reading the view also we would have > to read it from the cache instead of the session. > > please share your thoughts on this. Would greatly appreciate if you can > guide us through the implementation as well. > > > thanks > > parthiv >
