Hi all,
thanks for your suggestions!
@Martin, even when I override the setHeaders method, Safari seems to ignore the
settings „disableCaching“.
@Override
protected void setHeaders(WebResponse response) {
super.setHeaders(response);
response.disableCaching();
}
br Chris
> Am 11.05.2015
You can create a pixel image and compare a session time on the server..
Most likely the solution used by Google Analytics...
Em 11/05/2015 13:38, "Christoph Läubrich" escreveu:
> If you are really eager to do so (in fact this is some kind of user
> tracking that might be problematic as well as y
If you are really eager to do so (in fact this is some kind of user
tracking that might be problematic as well as you users might try to
block it ...) you can fire an AJAX call in the domReady and one in the
close callback or when clicking a link. In fact you can only GUESS the
time a user stay
https://github.com/apache/wicket/blob/32af2c8cc8985fc8a52f492d854dbf3206b7c243/wicket-core/src/main/java/org/apache/wicket/markup/html/WebPage.java#L206
Wicket pages by default send "do not cache me" response headers.
Safari should obey the rules.
Martin Grigorov
Wicket Training and Consulting
ht
Hi Martin,
Safari by default has turned cache on and therefore when clicking browser-back
the page is loaded from the browser’s cache.
Is there a way to circumvent this issue so that I can measure the time users
spent on a current page somehow?
best regards, Chris
> Am 11.05.2015 um 08:22 sc
Wicket pages are not cached by default.
Navigating back in the browser should make a request to the server and
execute the RENDER phase (onConfigure, onBeforeRender, onRender,
onAfterRender, onDetach).
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, May 11, 2
Hmm, it can be a browser cache issue, or the Wicket cache.. Try call the
setVersioned(false)
Em 10/05/2015 18:09, "Chris" escreveu:
> Thanks but the methods such as onBeforeRender seem not be called on
> browser back.
>
> Chris
>
>
> > Am 10.05.2015 um 22:54 schrieb Marcel Barbosa Pinto <
> marc
Thanks but the methods such as onBeforeRender seem not be called on browser
back.
Chris
> Am 10.05.2015 um 22:54 schrieb Marcel Barbosa Pinto :
>
> You could override the onRender method that is executed every time the page
> is rendered on the browser.
> Em 10/05/2015 17:43, "Chris" escreveu
You could override the onRender method that is executed every time the page
is rendered on the browser.
Em 10/05/2015 17:43, "Chris" escreveu:
> Hi all,
>
> I would like to measure the time the user stays at a certain page. I would
> do this by querying the system’s time when loading the page (in
Hi all,
I would like to measure the time the user stays at a certain page. I would do
this by querying the system’s time when loading the page (in the page
constructor) and the system time when clicking on a link that refers the user
to the next page.
However, if the user hits the browser back
10 matches
Mail list logo