Ahh... I was getting worried that it synchronous per page-resource (as opposed to per client), the last person could be waiting for a while!
So essentially it's single threaded per client (or session) which is pretty much par for the course, and not a problem that I can see :) - Brill Pappin -----Original Message----- From: Eelco Hillenius [mailto:[EMAIL PROTECTED] Sent: Saturday, May 17, 2008 1:03 AM To: users@wicket.apache.org Subject: Re: Thread safety for components On Fri, May 16, 2008 at 7:50 PM, Brill Pappin <[EMAIL PROTECTED]> wrote: > Does that mean that under heavy load, hitting the index page for > instance, I can expect clients to block as each request is processed? Yes, requests to pages/ components that belong to the same pagemap in a session are handled synchronously. Images and other resources like javascript and css files are handled asynchronously. Different clients never block each other. Eelco --------------------------------------------------------------------- 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]
