You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2008/04/20 20:46:26 UTC
[jira] Updated: (WICKET-617) Optimize JavaScript and CSS downloads
[ https://issues.apache.org/jira/browse/WICKET-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-617:
--------------------------------------
Fix Version/s: (was: 1.4-M1)
1.4-M2
> Optimize JavaScript and CSS downloads
> -------------------------------------
>
> Key: WICKET-617
> URL: https://issues.apache.org/jira/browse/WICKET-617
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Jonathan Locke
> Fix For: 1.4-M2
>
>
> It may be necessary to prevent extra round-tripping for high-traffic sites because most browsers cannot load JavaScript or CSS in parallel. It would be good to provide a facility where different Wicket components (including user components) can all contribute JavaScript to a single JS download so there are no round-trips. Failing this, a simple boolean setting that would prevent Wicket from automatically adding wicket-ajax.js, modal.js and so forth would allow people with high-traffic web sites to paste the JS together by hand (without having to maintain a branch of wicket). Obviously, this is not going to be addressed for 1.3, but it would be nice to consider for 1.4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.