diff options
| author | 2018-10-14 00:35:43 +0200 | |
|---|---|---|
| committer | 2018-10-14 00:35:43 +0200 | |
| commit | 1cc891be35c50ad3fd1fcc3498a08f7f46462d35 (patch) | |
| tree | cfc5c2bbed29a9e4996f19624d57b7633f7653c2 /p/scripts | |
| parent | ee902ee7c4370421802768c3105ba269a4f97b16 (diff) | |
Remove some preload / prefetch (#2040)
* Remove next prefetch
This approach was only efficient in the specific case when no change was
made (no mark-as-read, favourites, tags), and useless in the other
situations.
Removed to reduce server load.
* Remove next prefetch from JavaScript too
* Remove some preload / prefetch
While useful for the first request, those preload / prefetch hints are
slightly negative for the following requets, especially server-side,
e.g. generating one log entry in Apache, and a bit more network traffic.
* Revert mistake
* Remove comment
https://github.com/FreshRSS/FreshRSS/pull/2040#discussion_r223214915
Diffstat (limited to 'p/scripts')
| -rw-r--r-- | p/scripts/main.js | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/p/scripts/main.js b/p/scripts/main.js index cac2e8706..1495998b0 100644 --- a/p/scripts/main.js +++ b/p/scripts/main.js @@ -1170,7 +1170,6 @@ freshrssLoadMoreEvent.initEvent('freshrss:load-more', true, true); function init_load_more(box) { box_load_more = box; - document.body.dispatchEvent(freshrssLoadMoreEvent); var $next_link = $("#load_more"); @@ -1181,12 +1180,6 @@ function init_load_more(box) { } url_load_more = $next_link.attr("href"); - var $prefetch = $('#prefetch'); - if ($prefetch.attr('href') !== url_load_more) { - $prefetch.attr('rel', 'next'); //Remove prefetch - $.ajax({url: url_load_more, ifModified: true }); //TODO: Try to find a less agressive solution - $prefetch.attr('href', url_load_more); - } $next_link.click(function () { load_more_posts(); |
