Hi,
From: "Igor Vaynberg" <[EMAIL PROTECTED]>
well, at some point the server calls will start returning right? and so
xmlhttprequest objects will start being reused. it will consume memory to a
certain point and then stop. if you ask me 100ms for an ajax update is
unreasonable anyways,
Well, that depends. Our applications mostly run in local ethernet,
have quite fast servers and usually less than 100 users with Apache Tomcat.
I understand that things woudn't work this fast for a public internet site,
but for a local, small application it is doable. Actually, we did a web
application using dhtml to update values with 250 ms cycle a few years
ago and it has been working really well.
this is what jetty 6 continuations are for which would
be relatively simple to integrate into wicket as an alternative for ajax
self updating behaviors.
Is this jetty-only ? We have been rather commited on using tomcat.
Ari S.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
