[Seaside-dev] Ajaxifier updates

[Philippe Marschall]

On Sat, Sep 1, 2012 at 5:33 PM, Lukas Renggli <renggli at gmail.com> wrote:
> Hi Philippe,
>
> Using the history API seems definitely a good idea.
>
> For the redirect I am missing the context. Why does the Ajaxifier need
> to save the action URL? When using the back button you should not
> trigger the actions again, but jump back to the render URL.

Correct, but it used to save the action URL. The reason it did so is
because there was no way of finding out the URL of the render
continuation since all the links on the page are to action
continuations. The Ajaxifier used to add a _n to the links and save
those URLs. However that still means they are combined action/render
pages which means the callbacks will be executed again. Removing the
_n causes a redirect to the render continuation but there is no way in
Javascript to find out to which page a redirect happened. That's why
we added the header.

Cheers
Philippe