I wouldn't spend too much time worrying about the possibility of a mistake that big at this point! There are 20 programmers on this project at this point and almost all of them are architects with many years of experience. Wicket is being used by many thousands of users on hundreds if not thousands of projects. We used it at a venture funded startup called thoof to create a fully scalable website with benchmarks you can read about here:
http://blog.thoof.com/index.php/geekery/build-to-scale-our-web-architecture/ I know of several Fortune 500 companies using Wicket and even one website with millions of users that is converting to Wicket to save on maintenance costs. While Wicket is not stateless, it is quite efficient for a stateful framework with an excellent programming model. My expectation is that stateful frameworks with good programming models will win in the end. Even today, Wicket applications spend most of their time waiting for databases and services. As hardware improves, this equation will only favor Wicket more and more. Brill Pappin wrote: > > 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] > > > -- View this message in context: http://www.nabble.com/Thread-safety-for-components-tp17265324p17288470.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
