Hi Johan, Thanks a lot for your answer!
On 2/23/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
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)
I don't have a strong deadline, and I use java6, so I guess using 2.0 is
better.
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?
Maybe polling is better for what I need, I'm still not comfortable with the
http protocol and how server side notifications can be done. My problem is
that I have page for which I would like to be able to serve a lot of
clients, some of which will need to be updated frequently and others won't.
And I can't really guess which one need frequent updates. So I'm wondering
if polling from all clients every 5 seconds is better than using an open
connection for each which only sends data when needed. I don't really know
the cost of establishing a connection on the server and processing it just
to know that nothing has changed. If this cost is not important, polling
should be ok. Otherwise, maybe an open connection would better fit my need?
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.
Yes, I understand, but it's a good thing to know that other simple pages can
be served without a session.
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..
Do you have any recommendation about the right server?
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.
Ok. What I still don't see clearly enough is what are the advantages of the
2.0 stream over the 1.3. Could you give me some quick insight on what are
the major differences between the two?
BTW, thanks a lot to all the wicket team, wicket is really different from
all other frameworks I've seen so far, very refreshing!
- Xavier
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
-------------------------------------------------------------------------
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
