Alternatively, if this does not make any sense or is not possible at all,
would it be an option to approach this from the opposite direction, i.e.
make the pages really stateless, but still store them in the application
level cache so they don't have to be fully re-created for every Ajax call?
On
Hi Martin,
Yes, I tried that, but what happens is this:
When a user clicks on the an an Ajax link on a page that is not in the
application cache, the whole page gets refreshed and nothing else happens.
This is due to the following code in ListenerInterfaceRequestHandler:
if
Hi,
You can setup a no-op IPageStore.
This way there won't be a call to ISerializer#serialize(Object) at all.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jan 12, 2017 at 11:53 AM, Thomas Heigl wrote:
> I forgot to add:
>
> We are
I forgot to add:
We are using the HTML5 History API to push state to the (bookmarkable) URL,
so a page can be re-created with *all* state from the URL alone.
Thomas
On Thu, Jan 12, 2017 at 11:47 AM, Thomas Heigl wrote:
> Hi all,
>
> I'm looking for a solution to avoid