> My aim would be to push requests towards statelessness as much as possible. > Noticing this some guys have told me that "maybe wicket is not for this". > Considering that atleast 20% of the requests will be session based, do you > suggest using wicket.
You should also consider why you want to use Wicket in the first place. If your UI requirements aren't all that complicated, and you work with a very small team (say 2 people), Wicket may not buy you much compared to - say - just using JSPs, JAXRS and jQuery. If on the other hand, your development team is larger (say 3 or 4+ people), and/ or you have to maintain a complex UI, where you probably want to reuse widgets, move them around at will etc, you can benefit considerably from using a component based framework like Wicket. I would agree with others here that 10K concurrent users shouldn't be a problem; small cluster or maybe even a single machine should cut it, though compared to not using a stateful framework, you'll have to deal with session replication or sticky sessions in a cluster, and probably (depending on well you implemented things of course!) less beefy hardware requirements. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
