A bit of the application lets you add items to a list using AjaxFallbackButton. All works fine if you click the buttons slowly but if I click quickly I get exceptions that look like my code is running concurrently (nullpointer where it can't happen if running in a single thread).
What behaviour is Wicket aiming to implement for Ajax and threading? Matej Knopp-2 wrote: > > Can you be more specific? What kind of concurrency issues? > > -Matej > > On 9/7/07, Sam Hough <[EMAIL PROTECTED]> wrote: >> >> oops, I posted on old forum... >> >> http://www.nabble.com/threading-question-tf841003.html >> >> [all request serialised on Session object] >> >> Is this true even for Ajax requests? Is whole life cycle effectively >> single >> threaded for a single session? >> >> I think I'm seeing a concurrency issue in my website (Wicket 1.3-beta3 >> and >> lots of AjaxFallbackButton, I did listen to Igor)... >> >> Obviously would be tempting to sync on the Session but might break lot of >> the usability advantages of Ajax... >> >> Anybody got any top tips? >> -- >> View this message in context: >> http://www.nabble.com/threading-issues---continued-tf4400569.html#a12552735 >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > 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#a12553207 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
