yes, state is mainly kept in server side components by design (programming model and security are two good reasons for this). however, state can also reside in url parameters (bookmarkable page links) if you explicitly put it there. and then of course there's javascript / ajax.
Robert ... wrote: > > > Something else related to this is if I can have a Link where I can add > parameters to in javascript. > Looking at Wicket I get the feeling that the state is purely something > that > is kept in pages and components > with its associated models. There does not seem to be room for the client > browser to keep any state. > I actually have a whole model-view-controller system in javascript for > certain complicated situations. > > I tried to look at how a Tree component works, and see if I could learn > something by looking at how it's called. > But that part was just magic to me :) > > Robert > > -- View this message in context: http://www.nabble.com/Tapestry--%3E-Wicket-%7C-Action-Service-tf3408177.html#a9521396 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- 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
