> That is sending state back to the client - I'm talking about passing a > key back, just not in the URL.
Yeah, I got that. What you mean is the part that now makes the path to the request target (like pagemap/ page(version)/ component combi). > But yes, you are showing that hidden > fields can be used. That was my point. The mechanism is the same except that in whereas client state saving would get the state back by deserializing, your proposal would get it by using that key etc. In fact, that part really isn't much more than configuring a custom target resolver. > I'm sure ways could be worked around to get links to > work (bit of javascript to do a post via a hidden form). Yeah. Probably best by using postprocessing like that client state saving experiment doesn. That's the least intrusive and most robust imo. > > Of course, any contributions in the form of patches are always welcome > > and might serve as a good starting point for further discussion :) > > Heh, well, wouldn't that be nice. I'd love to have some time to do some > open source coding. Instead I just make do with writing emails :-) Damn users and incubation mentors ;) Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
