You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Sam Hough <sa...@redspr.com> on 2008/01/04 16:54:52 UTC

Wicket/Ajax history support

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 :(

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. 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.

Cheers

Sam
-- 
View this message in context: http://www.nabble.com/Wicket-Ajax-history-support-tp14619281p14619281.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket/Ajax history support

Posted by Eelco Hillenius <ee...@gmail.com>.
> Anyway, all I can say is I really like Wicket and I'm sorry if I offended
> anybody.

I don't think you did. We've got thick skin most of the time :-)

> I love a frank tech debate

We too. No worries.

Eelco

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket/Ajax history support

Posted by Sam Hough <sa...@redspr.com>.


> Yeah, it's a tough problem to solve. Any concrete help (meaning
> executable code) is welcome.
> 
I think my boss is quite into sharing code so will see if we come up with
anything good.



> 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). 
> 
I think that is very true. I had only meant to say that I would heartily
recommend Wicket for that particular rough set of requirements. For
applications component UIs is definitely the way to go and if you want to
support all clients/browsers then Wicket (Tapestry?) is the only thing I can
think of to do the job. 



> 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. 
> 
I really, really didn't mean to say it wouldn't scale. However if it was my
neck on the block to develop and support a medium to high traffic website
I'd like something simpler.

Anyway, all I can say is I really like Wicket and I'm sorry if I offended
anybody. I love a frank tech debate and probably forgot how much time some
people have put into this project. Having a few patches accepted for
projects that are a fraction as popular as Wicket is the most I've done.

Cheers

Sam



-- 
View this message in context: http://www.nabble.com/Wicket-Ajax-history-support-tp14619281p14647734.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Wicket/Ajax history support

Posted by Eelco Hillenius <ee...@gmail.com>.
On 1/4/08, Sam Hough <sa...@redspr.com> 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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org