Hi Johan,
I agree. Still, bookmarkability (also a requested feature) is exactly
the reason for going along with having nice URLs for every page, even
after an AJAX update. I have a prototype that uses Realysimplehistory to
allow a page to be bookmarkable after an AJAX update. Not sure yet how
On 2/5/08, Erik van Oosten [EMAIL PROTECTED] wrote:
Hi Johan,
Anyways, the fact remains that nice URLs can be important for some
Wicket projects, despite what average Joes may look at.
A big me too to that!
We have a specific (and I beleive wise) requirement for bookmarkable,
human readable
If you use HybridUrlCodingStrategy the page is bookmarkable after ajax
request. It can be recreated, but without the changes that ajax
request made to it. But this is not just ajax request, you have same
problems when using regular request. Wicket doesn't allow you to
reflect fine grained changes
