Hi Ben, Have you tried using Tapestry's client persistence? I'm not up to speed with how well it works now.
A slightly more significant departure might be to start replacing your pages and components with stateless rest endpoints using Tynamo's tapestry-resteasy, a piece at a time. We've done this with a couple of our components, moving them into angularjs. I'd also suggest that trying to stop users opening multiple tabs for internal links (e.g. target="_blank") might alleviate the multiple tab problem a little in the short term. Cheers, Luke On Tue, Apr 15, 2014 at 11:14 AM, Ben Titmarsh <ben.titma...@hotmail.co.uk>wrote: > Hi Everyone, > > My application is under a level of load where I am starting to regret a > somewhat naive over reliance on the @Persist annotation. My pages probably > contain far too much state and as a result my memory utilisation is going > through the ceiling and I'm having to perform semi-regular restarts. > > In addition the lack of conversational state means that I have issues with > multiple tabs being open - same old story I guess. > > So what I'd like to know is how should I be tackling this in Tapestry 5.3? > I had a look around and found the third party Tynamo library that has a > conversational state implementation but it doesn't look like it's seen an > update for 3 years. Is this still the best way forward? > > I'm probably going to need to tackle this in baby steps and will likely > start out by littering my code with > componentResources.discardPersistentFieldChanges() but I'd like to know > what other approaches have worked for you guys. > > Thanks a lot, > Ben. >
