> Yeah, it's a tough problem to solve. Any concrete help (meaning
> executable code) is welcome.
>
I think my boss is quite into sharing code so will see if we come up with
anything good.
> Wicket is not the answer to everything either. No-one on the team is
> dogmatic on this. I think Wicket is especially useful for complex
> applications that resemble desktop apps (but then with bookmarking
> etc).
>
I think that is very true. I had only meant to say that I would heartily
recommend Wicket for that particular rough set of requirements. For
applications component UIs is definitely the way to go and if you want to
support all clients/browsers then Wicket (Tapestry?) is the only thing I can
think of to do the job.
> But that doesn't mean that you can only use it for that. It
> scales well enough to handle lots of users, and we've always made sure
> that Wicket would behave as good as it can in clusters, and is
> optimized as well as we can.
>
I really, really didn't mean to say it wouldn't scale. However if it was my
neck on the block to develop and support a medium to high traffic website
I'd like something simpler.
Anyway, all I can say is I really like Wicket and I'm sorry if I offended
anybody. I love a frank tech debate and probably forgot how much time some
people have put into this project. Having a few patches accepted for
projects that are a fraction as popular as Wicket is the most I've done.
Cheers
Sam
--
View this message in context:
http://www.nabble.com/Wicket-Ajax-history-support-tp14619281p14647734.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]
