> Ok. Now I've read about detachable models and terracotta things become > much clearer to me. > The question about how many concurrent requests one server with wicket > can serve, still stands. > I've read about 500 concurrent requests with 64M heap for wicket 1.3 in > parallel thread. Any other data/tests available?
The thing with public test results imo is that you always have to be careful how to interpret them, and that they typically are written to prove a point. So the best thing to do it do em yourself and draw your own conclusions. I would be surprised if Wicket wouldn't perform well enough for your purposes. There is overhead, but the overhead is tweakable to some extend (e.g. by using a proper session store and by working with stateless pages or not etc). Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
