I'd like to discuss locking of the session for dynamic resources. For things like images and possibly reports, it might be a better idea *not* to lock.
Eelco ---------- Forwarded message ---------- From: Eelco Hillenius <[EMAIL PROTECTED]> Date: Jan 19, 2006 11:47 AM Subject: Re: [Wicket-user] threading question To: wicket-user@lists.sourceforge.net Uhm. Yeah, I guess if the process itselve is stuck, you'll have that problem. I didn't read well :) It's a good point for resources actually. With shared resources you won't have problems like these (as they are not synchronized), but in the case of dynamically created resources like reports and images you have. Locking is more faingrained in 1.2 than in 1.1, but we still have something to tweak here it seems. Anyone any ideas? Eelco On 1/19/06, Matej Knopp <[EMAIL PROTECTED]> wrote: > Are you sure? At least in 1.1, I have a PDF report generator link, and > while the pdf is generating, the session is locked and no other request > (From the same user) can touch it, so all other requests are waiting. > > -Matej > > Eelco Hillenius wrote: > > That won't ever happen. It is not possible for the code to be 'stuck' > > in a synchronized block. > > > > Eelco > > > > > > On 1/19/06, karthik Guru <[EMAIL PROTECTED]> wrote: > >> If we synchronize on session and if the request does'nt return what > >> happens ? > >> I mean if i click on a report generation link and for some reason it > >> takes too much time to finish, Can the user go to some other page by > >> ignoring the previous request to generate a report. Do we have to > >> start another user session from here. > >> > >> > >> ------------------------------------------------------- > >> This SF.net email is sponsored by: Splunk Inc. Do you grep through log > >> files > >> for problems? Stop! Download the new AJAX search engine that makes > >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > >> http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642 > >> _______________________________________________ > >> Wicket-user mailing list > >> Wicket-user@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/wicket-user > >> > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 > > _______________________________________________ > > Wicket-user mailing list > > Wicket-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
