you're not the only one. As for long running database transactions, in our system we opted for splitting off a separate thread to do the work. Our users get notified on the progress using an ajax progress counter.
Martijn On 6/22/06, jan_bar <[EMAIL PROTECTED]> wrote: > > I'm I the only one with this issue? > > Hi, > > I see your points. In my opinion, *any* database query (but not only > database) can be long operation. At that time your code is sitting in idle > loop waiting for database (located on another PC). In that time the CPU can > do other useful job for the same client (session). I pointed out another use > case with images from database, see my other response. If the session is not > locked, the image will appear in parallel (quicker), while with locked > session, they will appear one by one (slower, because of lost time waiting > for database). > > Jan > > > > > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Wicket-develop mailing list > Wicket-develop@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-develop > -- Download Wicket 1.2 now! Write Ajax applications without touching JavaScript! -- http://wicketframework.org All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
