Didier, I was under the impression your prefetching issues were related to the google web-accelerator gizmo, am I wrong? Sameer, a prefetching feature sounds like a good idea, definitely to be implemented via a plugin, and turned off by default if we decide to put it in the default distribution, though. On 9/13/05, Didier Deshommes <dfdeshom at ncsu.edu> wrote: > On Tue, 13 Sep 2005, Sameer D'Costa wrote: > > > Does anyone have any strong views on link prefetching hints? Currently I > > view my feeds folder-by-folder. After reading each folder, I click mark > > as read and then it goes off to the next folder. If in the time I took me > > to scan a folder, the browser would use idle time to prefetch the next > > page, it would be useful. The cons are that it would increase bandwidth > > usage. > > This is strange. When I was complianing about excessive bandwidth useage > on this list, prefetch was the culprit. Specifically, FF prefetched links > when I had mod_rewrite enabled for Gregarius. Since then, I have not used > the mod_rewrite option and have disabled prefecth from FF. So is this > option necessary? It seems like FF does prefetching when it sees it fit. > > > > > Currently mozilla browsers support the rel=prefetch tag for links. Google > > uses it sometimes, so that you can prefetch the top search result. > > > > I was thinking of putting navigation links for the next and previous > > folders and categorys (we currently have it only for items and channels). > > > > And after that, Depending on what you guys think we could add prefetch > > links to the next folder either in the code (with a YACO?) or via a > > plugin. > > > > Sameer > > _______________________________________________ > > gregarius-dev mailing list > > gregarius-dev at sinless.org > > http://sinless.org/mailman/listinfo/gregarius-dev > > > _______________________________________________ > gregarius-dev mailing list > gregarius-dev at sinless.org > http://sinless.org/mailman/listinfo/gregarius-dev >