On 1/4/08, Sam Hough <[EMAIL PROTECTED]> wrote: > > What is the best bet for supporting the back button and bookmarking in Ajax > heavy Wicket 1.3? > > I saw this ticket which I think covers what I'm on about: > http://issues.apache.org/jira/browse/WICKET-271 > > So far we are thinking about marking which bean properties of components > should be recorded for history and bookmark purposes and then shoving these > into #bit after the URL. Then need a bit of JS to send that to the server... > Obviously this will be a lot of work :(
Yeah, it's a tough problem to solve. Any concrete help (meaning executable code) is welcome. > Matej : Sorry if I gave the wrong impression on TheServerSide (as x.y) about > Wicket's performance. I thought I was saying pretty much as matt raible had > by putting it in the "Internal, more desktop-like applications that are > stateful" category. We don't always agree with Matt either :-) > Doing server side component based framework is tough and > you guys have done an amazing job. I'm very, very grateful that Wicket has > saved me from struts 2 in my current job. Wicket is not the answer to everything either. No-one on the team is dogmatic on this. I think Wicket is especially useful for complex applications that resemble desktop apps (but then with bookmarking etc). But that doesn't mean that you can only use it for that. It scales well enough to handle lots of users, and we've always made sure that Wicket would behave as good as it can in clusters, and is optimized as well as we can. Also, if your application is simple, you might want to consider a 'lighter' approach (like plain HTML & JavaScript/ Ajax - webservices or REST). But then again, if you are already comfortable with Wicket, why not save yourself a bunch of time and just use that? Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
