You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Robert McGuinness (Created) (JIRA)" <ji...@apache.org> on 2011/11/11 03:38:51 UTC
[jira] [Created] (WICKET-4216) Enhance
AjaxServerAndClientTimeFilter to use HTML5's Navigation Timing API
Enhance AjaxServerAndClientTimeFilter to use HTML5's Navigation Timing API
--------------------------------------------------------------------------
Key: WICKET-4216
URL: https://issues.apache.org/jira/browse/WICKET-4216
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 1.6.0
Environment: All
Reporter: Robert McGuinness
Priority: Trivial
in AjaxServerAndClientTimeFilter.java, instead of:
map.put("clienttime", "' + (new Date().getTime() - clientTimeVariable)/1000 + 's");
Wicket could use:
map.put("clienttime", "' + (new Date().getTime() - performance.timing.navigationStart)/1000 + 's");
which could output something like:
Server parsetime: .01s, User-perceived page loading time: .02s
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-4216) Enhance
AjaxServerAndClientTimeFilter to use HTML5's Navigation Timing API
Posted by "Martin Grigorov (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151109#comment-13151109 ]
Martin Grigorov commented on WICKET-4216:
-----------------------------------------
I think this ticket should be "Trivial" :-)
NavigationTiming is not widely supported. It has been added in Firefox in ver. 7. I'm not sure what is the state in IE but I'd bet IE7/8 don't have it.
Maybe we should move that logic to wicket-ajax-debug.js (the code for the Ajax Debug Window) because status bar is also not that common these days and window.defaultStatus is not immediately visible anymore. There we can add check for support of 'performance' and fallback to the old code.
> Enhance AjaxServerAndClientTimeFilter to use HTML5's Navigation Timing API
> --------------------------------------------------------------------------
>
> Key: WICKET-4216
> URL: https://issues.apache.org/jira/browse/WICKET-4216
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.6.0
> Environment: All
> Reporter: Robert McGuinness
> Priority: Trivial
>
> in AjaxServerAndClientTimeFilter.java, instead of:
> map.put("clienttime", "' + (new Date().getTime() - clientTimeVariable)/1000 + 's");
> Wicket could use:
> map.put("clienttime", "' + (new Date().getTime() - performance.timing.navigationStart)/1000 + 's");
> which could output something like:
> Server parsetime: .01s, User-perceived page loading time: .02s
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (WICKET-4216) Enhance
AjaxServerAndClientTimeFilter to use HTML5's Navigation Timing API
Posted by "Martin Grigorov (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151109#comment-13151109 ]
Martin Grigorov edited comment on WICKET-4216 at 11/16/11 9:49 AM:
-------------------------------------------------------------------
I think this ticket shouldn't be "Trivial" :-)
NavigationTiming is not widely supported. It has been added in Firefox in ver. 7. I'm not sure what is the state in IE but I'd bet IE7/8 don't have it.
Maybe we should move that logic to wicket-ajax-debug.js (the code for the Ajax Debug Window) because status bar is also not that common these days and window.defaultStatus is not immediately visible anymore. There we can add check for support of 'performance' and fallback to the old code.
was (Author: mgrigorov):
I think this ticket should be "Trivial" :-)
NavigationTiming is not widely supported. It has been added in Firefox in ver. 7. I'm not sure what is the state in IE but I'd bet IE7/8 don't have it.
Maybe we should move that logic to wicket-ajax-debug.js (the code for the Ajax Debug Window) because status bar is also not that common these days and window.defaultStatus is not immediately visible anymore. There we can add check for support of 'performance' and fallback to the old code.
> Enhance AjaxServerAndClientTimeFilter to use HTML5's Navigation Timing API
> --------------------------------------------------------------------------
>
> Key: WICKET-4216
> URL: https://issues.apache.org/jira/browse/WICKET-4216
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.6.0
> Environment: All
> Reporter: Robert McGuinness
> Priority: Trivial
>
> in AjaxServerAndClientTimeFilter.java, instead of:
> map.put("clienttime", "' + (new Date().getTime() - clientTimeVariable)/1000 + 's");
> Wicket could use:
> map.put("clienttime", "' + (new Date().getTime() - performance.timing.navigationStart)/1000 + 's");
> which could output something like:
> Server parsetime: .01s, User-perceived page loading time: .02s
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira