if your deadline is still 6+ months away, you could start using 2.0 (if you
can use java5)
if it is shorter you should use 1.3
(at least that is how i see it currently)
Why wouldn't a polling ajax behavior work? Do you really want to have an
constant open connection somehow?
(also a thing the servlet spec is currently now really build for, but jetty
does go around it i guess)
Why do you need it exactly? Does the server comes with new data constantly
that you want to see as soon as possible?
We did improve the memory usage in wicket 1.3 and 2.0 by storing much less
in the session
And you can lazy delay a session now yes. But if you have constant ajax
request then currently that page would be in memory on the server side.
If you want a constant connection to the server then do choose the right
server (that uses NIO and so on)
because the current servlet way of thread per request is really not scalable
then..
All lazy delayed sessions stuff did come from 2.0 to 1.3 so 2.0 should all
have that. Currently there are some optimizes in 1.3 that needs to be
ported to 2.0 again. But this will happen soon.
johan
On 2/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
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.0 provide 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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
