Seam has support for back button. However, i'm running into seam projects that have decided to limit back button support by limiting the amount of conversations that are kept in memory. Keeping everything in memory just uses too much memory and is not realistic. Ho开发者_C百科wever, this caused problems for the users, as they are seeing unexpected behaviour when moving back to pages used in older conversations. (currently targetting 1600 concurrent users on 16 jboss instances, each instance has 8gb) What's the best way to implement back button support?
Without changing the inner workings of seam, which unfortunately is quite stateful, or using some other cache on top, the only easiest option I see is to increase conversation-timeout
精彩评论