[jira] Commented: (WICKET-617) Optimize JavaScript and CSS downloads
[ https://issues.apache.org/jira/browse/WICKET-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501651 ] Eelco Hillenius commented on WICKET-617: not only that, it also zips by default. http://chillenious.wordpress.com/2007/02/10/automatic-comment-and-whitespace-stripping/ > 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 > > 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.
[jira] Commented: (WICKET-617) Optimize JavaScript and CSS downloads
[ https://issues.apache.org/jira/browse/WICKET-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501650 ] Jonathan Locke commented on WICKET-617: --- Ah, it looks like JavascriptResourceReference already does this. Nice work Matej! > 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 > > 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.
[jira] Commented: (WICKET-617) Optimize JavaScript and CSS downloads
[ https://issues.apache.org/jira/browse/WICKET-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501645 ] Jonathan Locke commented on WICKET-617: --- Something similar to this: http://dean.edwards.name/packer/ > 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 > > 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.
[jira] Commented: (WICKET-617) Optimize JavaScript and CSS downloads
[ https://issues.apache.org/jira/browse/WICKET-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501644 ] Jonathan Locke commented on WICKET-617: --- We could provide a production mode filter that strips whitespace and comments from JS files. There are quite a lot of comments in good javascript code and there's no sense in downloading all that in a production environment. By aggregating all the JS, we can get the benefits of stripping out unneeded comments all from a single setting. > 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 > > 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.
