Fossil SCM
Updated javascript.md page to track recent developments.
Commit
3a1d3cc2dc9e566225f63bacd90f496b0109c6bddeaecba14e794cf0c893cf25
Parent
88ff2642d3bf0ad…
1 file changed
+5
-5
+5
-5
| --- www/javascript.md | ||
| +++ www/javascript.md | ||
| @@ -52,24 +52,24 @@ | ||
| 52 | 52 | rehash these same arguments on the [forum][ffor], we distill the common |
| 53 | 53 | ones we’ve heard before and give our stock answers to them here: |
| 54 | 54 | |
| 55 | 55 | 1. “**It increases the size of the page download.**” |
| 56 | 56 | |
| 57 | - The heaviest such pages served by Fossil only have about 8 kB of | |
| 57 | + The heaviest such pages served by Fossil only have about 15 kB of | |
| 58 | 58 | compressed JavaScript. (You have to go out of your way to get Fossil |
| 59 | 59 | to serve uncompressed pages.) This is negligible, even over very |
| 60 | 60 | slow data connections. If you are still somehow on a 56 kbit/sec |
| 61 | 61 | analog telephone modem, this extra script code would download in |
| 62 | - about a second. | |
| 62 | + a few seconds. | |
| 63 | 63 | |
| 64 | 64 | Most JavaScript-based Fossil pages use less code than that. |
| 65 | 65 | |
| 66 | - Atop that, Fossil 2.12 adds new script delivery methods with | |
| 67 | - aggressive caching enabled so that typical page loads will skip | |
| 66 | + Atop that, Fossil sends HTTP headers to the browser that allow it | |
| 67 | + to perform aggressive caching so that typical page loads will skip | |
| 68 | 68 | re-loading this content on subsequent loads. These features are |
| 69 | 69 | currently optional: you must either set the new [`fossil server |
| 70 | - --jsmode` option][fsrv] or the corresponding `jsmode` control line | |
| 70 | + --jsmode bundle` option][fsrv] or the corresponding `jsmode` control line | |
| 71 | 71 | in your [`fossil cgi`][fcgi] script when setting up your |
| 72 | 72 | [Fossil server][fshome]. That done, Fossil’s JavaScript files will |
| 73 | 73 | load almost instantly from the browser’s cache after the initial |
| 74 | 74 | page load, rather than be re-transferred over the network. |
| 75 | 75 | |
| 76 | 76 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -52,24 +52,24 @@ | |
| 52 | rehash these same arguments on the [forum][ffor], we distill the common |
| 53 | ones we’ve heard before and give our stock answers to them here: |
| 54 | |
| 55 | 1. “**It increases the size of the page download.**” |
| 56 | |
| 57 | The heaviest such pages served by Fossil only have about 8 kB of |
| 58 | compressed JavaScript. (You have to go out of your way to get Fossil |
| 59 | to serve uncompressed pages.) This is negligible, even over very |
| 60 | slow data connections. If you are still somehow on a 56 kbit/sec |
| 61 | analog telephone modem, this extra script code would download in |
| 62 | about a second. |
| 63 | |
| 64 | Most JavaScript-based Fossil pages use less code than that. |
| 65 | |
| 66 | Atop that, Fossil 2.12 adds new script delivery methods with |
| 67 | aggressive caching enabled so that typical page loads will skip |
| 68 | re-loading this content on subsequent loads. These features are |
| 69 | currently optional: you must either set the new [`fossil server |
| 70 | --jsmode` option][fsrv] or the corresponding `jsmode` control line |
| 71 | in your [`fossil cgi`][fcgi] script when setting up your |
| 72 | [Fossil server][fshome]. That done, Fossil’s JavaScript files will |
| 73 | load almost instantly from the browser’s cache after the initial |
| 74 | page load, rather than be re-transferred over the network. |
| 75 | |
| 76 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -52,24 +52,24 @@ | |
| 52 | rehash these same arguments on the [forum][ffor], we distill the common |
| 53 | ones we’ve heard before and give our stock answers to them here: |
| 54 | |
| 55 | 1. “**It increases the size of the page download.**” |
| 56 | |
| 57 | The heaviest such pages served by Fossil only have about 15 kB of |
| 58 | compressed JavaScript. (You have to go out of your way to get Fossil |
| 59 | to serve uncompressed pages.) This is negligible, even over very |
| 60 | slow data connections. If you are still somehow on a 56 kbit/sec |
| 61 | analog telephone modem, this extra script code would download in |
| 62 | a few seconds. |
| 63 | |
| 64 | Most JavaScript-based Fossil pages use less code than that. |
| 65 | |
| 66 | Atop that, Fossil sends HTTP headers to the browser that allow it |
| 67 | to perform aggressive caching so that typical page loads will skip |
| 68 | re-loading this content on subsequent loads. These features are |
| 69 | currently optional: you must either set the new [`fossil server |
| 70 | --jsmode bundle` option][fsrv] or the corresponding `jsmode` control line |
| 71 | in your [`fossil cgi`][fcgi] script when setting up your |
| 72 | [Fossil server][fshome]. That done, Fossil’s JavaScript files will |
| 73 | load almost instantly from the browser’s cache after the initial |
| 74 | page load, rather than be re-transferred over the network. |
| 75 | |
| 76 |