I must be slowing down or Sun is speeding up. Huge amounts of stuff in 1.5 that I've not played with. From 1.1 to 1.2 it didn't seem that much to keep up with!?
Not sure we have really slow tasks (like classic booking ticket) but we are using Alfresco for some calls and that can be slow... Thread per sluggish request is heavy duty maybe would be better with messaging... Even if within same JVM. I'm having one of those "isn't Wicket wonderful weeks" ;) Somebody hits a problem and I just hunt through JavaDoc to find the correct Component to plugin. Not like struts 2 where I tried to do something simple only, a few hours later, finding something in the docs about "yes this sucks but only way to do it". Martijn Dashorst wrote: > > On 9/7/07, Sam Hough <[EMAIL PROTECTED]> wrote: >> Create a thread from within a servlet container...? Tut tut ;) > > Yeah, not the most elegant way since they are not monitored by the > container, but it sure does get the work done. And we have really nice > users that would never try to flood our server. :) > > And of course if you're on Java 5, you can create worker pools really > easy to limit the number of concurrent threads. > > Martijn > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0-beta3 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/threading-issues---continued-tf4400569.html#a12555539 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
