we tried that already but dismissed it wicket has no support for this and for these kind of things to work everything must be come a post you cant use any normal links.
also you are trading in memory for cpu speed and bandwidth which is in my eyes more expensive then memory or hd space Page expired shouldnt really happen anymore in wicket 1.3 and greater anyway so that is not a problem you should try to fix Do you have memory problems or are you trying to fix something that isnt even a problem? johan On Thu, Sep 17, 2009 at 23:05, dmitry1000001 dmitry1000001 < [email protected]> wrote: > Hi, > > Is it possible to get rid of sessions by automatically saving page state > directly to URL, not into session? > So, for example, this can look like: ?pagestate=<automatically serialized > state of the page> > Of course, this won't work when page has models with large state because of > URL length limit, but will work perfectly in lots of cases. > This solution would not sacrifice Wicket's stateful nature and solve "Page > expired" problem. > > If this requires some deep changes of Wicket itself, what parts of Wicket > are to look into? > > Thanks! >
