Somewhat, inside Tapestry 5. There will (eventually) be the ability to terminate the render if it goes on too long. However, getting "inside" a long database query to terminate it early is well beyond Tapestry's mandate.
On Fri, Apr 17, 2009 at 2:35 PM, Bogdan Stojkovic <[email protected]> wrote: > Thanks for answer, DB is optimized but very large, I'll try with > javascript...That's going to be a challenge; have you thought about > addressing this > either at the database end (optimize your database, indexes, etc.) or > at the client end (javascript to prevent re-submits)? > > On Thu, Apr 16, 2009 at 2:35 PM, Bogdan Stojkovic <[email protected]> wrote: >> Hi all, >> >> I have small problem, if anyone can help.... >> I'm using tapestry 4.1, in one page I have link in witch I go to DB, execute >> sql and > this result set is displayed in table. This sql execution takes >10sec. If in > that time > I click on link again -> tapestry engine init is happend, but old sql is > still executing > in background as zombi proces, as I think. With many users maniacly clicking > on same button > several times (with no reason to do that :-) ) or other links on page, I face > resource problem, > it takes more memory and in my log I see a lots of engine inits, application > is starting to > work mutch slower. >> >> Anyone have idea how to solve problem with clicking on other links on page >> while long > sql execution is in progress? (maybe to intercept this engine inits and check > for current > page status - but i do not know how?) >> >> Thanks, >> Bogdan -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
