well, you should ask howard lewis-ship about the first one, the 2nd one lies in the way it works - tapestry manages everything while wicket doesnt
the downside is more work to make a component compared to wicket, the upside are goodies like easier URLs... and even in tapestry a real-nice URL is some work to do - not as hasrd as to implement your own URL strategy in wicket but its not for free either... regards > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im Auftrag > von cowwoc > Gesendet: Dienstag, 21. November 2006 22:59 > An: [email protected] > Betreff: [Wicket-user] Tapestry 5 instantaneous reloads > > > Two questions about: > http://howardlewisship.com/blog/2006/10/tapestry-5-screencast-2.html > > 1) How did they get "instantaneous" page reloads working? > 2) How did they get their URLs to remain "nice" even though > the underlying state is changing? > > and what is the implications for Wicket? I suspect you > guys have seen this before. Can you please comment on why > Wicket does not do something similar? Is it something to do > with the amount of client-side state they use? > > Thanks, > Gili > > ------------------------------------------------------------------------- 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
