Our first try just failed. Because that had pretty huge performance issues and the pages are way bigger because of the serialized state everything needs then to be rewritten like a post, the list goes on and on.
At that point we just came the the conclusion that this was not the way to go. Currently the only stateless way of doing stuff is doing it a bit your self and push state into links/forms a bit that you then get back from the submit this will be improved in 1.5 (then we have better support for building the urls that you click on and so on) johan On Tue, Mar 24, 2009 at 11:47, Alex Objelean <alex_objel...@yahoo.com>wrote: > > After reviewing the Wicket feature list, I accidentally noticed the > following > statement: > "The next version of Wicket will support client-side models for zero-state > scalability". I am wondering if this feature will be indeed implemented in > (which?) next version or this is just some feature which sounds great for > marketability and will never by implemented? > > Thank you! > > Alex > -- > View this message in context: > http://www.nabble.com/Client-side-models-for-zero-state-scalability-tp22677847p22677847.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
