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.
