By removing the SoftReference in PageSourceImpl. You would get an
OutOfMemoryError directly when you reach memory limit and the GC would
not try to fix this by throwing away PageImpl instances.
So you would fail on you test env earlier. Otherwise things would come
up during Performance/Loadtests which usually is later.
Am 18.03.2015 um 22:01 schrieb Thiago H de Paula Figueiredo:
On Wed, 18 Mar 2015 04:44:10 -0300, Robert Schmelzer
<rob...@schmelzer.cc> wrote:
I do not agree with you on that point. Tapestry is designed to cache
the page. When you do not have enough memory to hold your pages
cached basically the system does not work as designed so you should
fail early.
How could Tapestry detect this situation to fail early?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
