You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/03/03 19:50:56 UTC
[jira] Created: (TAP5-549) JavaScript libraries should be combined
into a single request
JavaScript libraries should be combined into a single request
-------------------------------------------------------------
Key: TAP5-549
URL: https://issues.apache.org/jira/browse/TAP5-549
Project: Tapestry 5
Issue Type: New Feature
Components: tapestry-core
Affects Versions: 5.1.0.1
Reporter: Howard M. Lewis Ship
It should be possible to create a virtual resource under /assets that represents all the JavaScript libraries for a particular page. I envision this as a Base64 stream that is the actually a composite list of paths to the real JavaScript files; encoded in such a way that when multiple pages use the same set of JavaScript libraries, they can share a single stream.
The combined stream should be gzipped (if client supports it) and should be packed/minimalized. Some extra bookkeeping is needed to track what JS files were combined (the client tracks loaded JS libraries for when an Ajax partial update requires new libraries that were not required for the main page render, for example, a partial update that includes a form with client-side validation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-549) JavaScript libraries should be combined
into a single request
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-549:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> JavaScript libraries should be combined into a single request
> -------------------------------------------------------------
>
> Key: TAP5-549
> URL: https://issues.apache.org/jira/browse/TAP5-549
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> It should be possible to create a virtual resource under /assets that represents all the JavaScript libraries for a particular page. I envision this as a Base64 stream that is the actually a composite list of paths to the real JavaScript files; encoded in such a way that when multiple pages use the same set of JavaScript libraries, they can share a single stream.
> The combined stream should be gzipped (if client supports it) and should be packed/minimalized. Some extra bookkeeping is needed to track what JS files were combined (the client tracks loaded JS libraries for when an Ajax partial update requires new libraries that were not required for the main page render, for example, a partial update that includes a form with client-side validation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-549) JavaScript libraries should be combined
into a single request
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-549:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> JavaScript libraries should be combined into a single request
> -------------------------------------------------------------
>
> Key: TAP5-549
> URL: https://issues.apache.org/jira/browse/TAP5-549
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> It should be possible to create a virtual resource under /assets that represents all the JavaScript libraries for a particular page. I envision this as a Base64 stream that is the actually a composite list of paths to the real JavaScript files; encoded in such a way that when multiple pages use the same set of JavaScript libraries, they can share a single stream.
> The combined stream should be gzipped (if client supports it) and should be packed/minimalized. Some extra bookkeeping is needed to track what JS files were combined (the client tracks loaded JS libraries for when an Ajax partial update requires new libraries that were not required for the main page render, for example, a partial update that includes a form with client-side validation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-549) JavaScript libraries should be combined
into a single request
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-549.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.2
> JavaScript libraries should be combined into a single request
> -------------------------------------------------------------
>
> Key: TAP5-549
> URL: https://issues.apache.org/jira/browse/TAP5-549
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.1.0.2
>
>
> It should be possible to create a virtual resource under /assets that represents all the JavaScript libraries for a particular page. I envision this as a Base64 stream that is the actually a composite list of paths to the real JavaScript files; encoded in such a way that when multiple pages use the same set of JavaScript libraries, they can share a single stream.
> The combined stream should be gzipped (if client supports it) and should be packed/minimalized. Some extra bookkeeping is needed to track what JS files were combined (the client tracks loaded JS libraries for when an Ajax partial update requires new libraries that were not required for the main page render, for example, a partial update that includes a form with client-side validation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-549) JavaScript libraries should be combined
into a single request
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-549.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.2
> JavaScript libraries should be combined into a single request
> -------------------------------------------------------------
>
> Key: TAP5-549
> URL: https://issues.apache.org/jira/browse/TAP5-549
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.1.0.2
>
>
> It should be possible to create a virtual resource under /assets that represents all the JavaScript libraries for a particular page. I envision this as a Base64 stream that is the actually a composite list of paths to the real JavaScript files; encoded in such a way that when multiple pages use the same set of JavaScript libraries, they can share a single stream.
> The combined stream should be gzipped (if client supports it) and should be packed/minimalized. Some extra bookkeeping is needed to track what JS files were combined (the client tracks loaded JS libraries for when an Ajax partial update requires new libraries that were not required for the main page render, for example, a partial update that includes a form with client-side validation).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.