do you have any thoughts on a list of requirements for ajax support?
[EMAIL PROTECTED] wrote:
It has been stated by others on this list and I see it on the proposed 1.1 features, but I would like to stress that supporting "AJAX" should be the highest priority for wicket.
I believe that wicket has solid advantages over Tapestry/Struts/JSF, however, what will really turn interest toward wicket, and make it stand out from the crowd, would be solid support for AJAX.
Take a look at what echo is doing: http://www.theserverside.com/news/thread.tss?thread_id=32834
The echo demo really shows the advantages of Ajax for "web applications" in particular. Echo2 is very nice but it is highly application and programmer centric, which is nice for web apps with complex state that are not easily modeled with "html pages".
Sam
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
