why not step through the debugger and see, or create a quickstart and attach it to a jira issue
-igor On Tue, Mar 23, 2010 at 10:37 AM, Nikita Tovstoles <nikita.tovsto...@gmail.com> wrote: > Appreciate your reply. > > If the redirect to .version is *always* supposed to happen what would > be some reason for that failing to happen? For example (i am reaching > here) if there are problems serializing the page, is the behavior to > fall back to plain bookmarkable url (and not redirect)? > > Here's an example of a page mounted with HybridUrlCodingStrategy: > > http://rebatefinder.ecorebates.com/embedded/search/category?siteId=ca > > So, I'd expect it to redirect to: > http://rebatefinder.ecorebates.com/embedded/search/category.0?siteId=ca > > but no go. >> >> this fixes the general problem with ajax requests not changing the >> url, so if user presses refresh button in the browser the ajax changes >> are lost. >> >> suppose you land on /user/profile/15 url which is bookmarkable and you >> have a bunch of ajax panel swaps for differnet parts of the user's >> profile. if the user presses refresh, eg if ajax request is taking too >> long, the url that is refreshed is the original bookmarkable url and >> all the changes are lost. >> >> however, with the hybrid strategy the user will immediately be >> redirected to a .x suffix which gives them a stateful url that will >> keep the changes. >> >> at least that was the idea behind the hybrid coding strategy, the >> hybrid part being that it is both bookmarkable and stateful. >> >> -igor >> >> On Mon, Mar 22, 2010 at 7:39 PM, Nikita Tovstoles >> <nikita.tovsto...@gmail.com> wrote: >>> The javadoc for HybridUrlCodingStrategy says: >>> >>> Also to preserve state on refresh with ajax-only pages the >>> HybridUrlCodingStrategy does an immediate redirect after hitting >>> bookmarkable URL, e.g. it immediately redirects from /mount/path to >>> /mount/path.3 where 3 is the next page id. This preserves the page >>> instance on subsequent page refresh. >>> >>> We have a few pages mounted with this strategy - some do issue a >>> redirect to /mountpath.version on 1st request, others for some reason >>> do not. I am assuming that's because some are "ajax-only" while others >>> are not? if so, what a definition of an ajax-only page? Or - if that's >>> easier - in which cases would this strategy NOT issue a redirect to >>> .version URL? >>> >>> thanks >>> -nikita >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
