Hi All,
I'm currently evaluating wicket for a project, and I'm very impressed so far
by the design!
I would like to start some developments and I wonder which version would be
the best in my case. I don't plan to make a release in a short period of
time, and I'm not afraid of looking into the code and adapt to changes, so I
don't mind to work on a version under development. According to what I've
seen so far, features from 1.x branch seems ok to me, the only things I'm
concerned with are:
* I'll have to make heavy use of asynchronous refresh of some pages
triggered by the server. I've seen nothing to help with that with the
current wicket version except timer based ajax refresh. I've heard about
cometd, but I'm not familiar with this technology yet. I've seen that some
have worked on dojo integration, and I know that dojo provides cometd
integration, so I guess a version compatible with the work done on
wicket-dojo would be good
* scalability is one of my concerns, and according to what I've read it
seems that wicket 1.3 will provide some way to avoid opening a session when
it's not necessary. What is the status with that? What will wicket
2.0provide about that?
So, could any of you give me some recommendations?
Thanks in advance!
- Xavier
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
