On Wed, Jan 7, 2009 at 2:29 PM, Colin Davis <Colin at sq7.org> wrote: >> CAVEATS: >> - I'm really not convinced that the basic progress screen on its own >> will >> yield adequate performance. It could be improved significantly by some >> javascript, but the real worry is once a page has loaded, it may >> have inline >> images which are over 64k and therefore not in the container, or >> which are >> not in the container because the site is over 2MB total, or which >> are fetched >> from other freesites. With the default limit of 8 connections per >> server, >> especially if the user opens multiple freesites in tabs, this could >> be a >> serious slowdown. > > An alternative to the XULRunner solution might be to simply pre-fetch > image links from fproxy.
We are prefetching them already. And we have a config option for that. It's just too slow. > If we parse the incoming HTML, and request > all embedded links (CSS + Images) in parallel, it bypasses the > connection limit in browsers entirely. > > Requesting all of the images/css on a page on parse would be a > relatively quick and dirty solution, but would seem substantially > easier than the alternatives. > > Further, if this were later extended to pre-fetch all linked pages, it > would improve the user experience by making freenet seem much quicker. > The loading would happen while the user read page A, rather than while > he clicked and waited for page B to load. > > -CPD
