On Friday 19 June 2009 14:48:11 sashee wrote: > Ofc not. HTTP is stateless, so in standard ways it cannot be notified > when a tab is closed.
Yes I mean with javascript? > > On Fri, Jun 19, 2009 at 12:28 AM, Matthew > Toseland<t...@amphibian.dyndns.org> wrote: > > On Thursday 18 June 2009 17:02:06 sashee wrote: > >> With async image loading,activelinks will be loaded too. > >> As for the 21 secs. It can be decreased, but only to sacrifice > >> something else. 21 sec means the client can skip a keepalive, and fail > >> after the second. Since it's localhost, it's unlikely to fail even 1, > >> so it can be reduced to 11 sec. If we send keepalives more frequently, > >> it will consume more resources for all tabs to send them, but it will > >> reduce further the time needed to detect tab closes. It is easily > >> configured with constants though. > > > > There is no callback on a page being closed? > >> > >> sashee > >> > >> On Thu, Jun 18, 2009 at 11:33 AM, xor<x...@gmx.li> wrote: > >> > On Wednesday 17 June 2009 16:36:26 sashee wrote: > >> >> Hello folks! > >> >> > >> >> Some days ago, I've talked with nextgens about toadlet > >> >> continuations(it's asynchronous request processing), and he had a > >> >> point that when the user opens a site with lots of images, then it > >> >> needs many connections open for a long time, and it spawns many > >> >> threads at serverside, which is resource demanding and some OSes don't > >> >> allow. The browser has a maximum connection limit to the site, but the > >> >> user can overwrite it. But at the default, firefox opens only 2-3 > >> >> connections to fetch the images, this way freenet don't start all the > >> >> fetching, just what is requested. So one problem is that if a user > >> >> alters the browser's config, then it will result many threads, if not, > >> >> then freenet can't download all the content simultanously. > >> >> I think with pushing, I'm working on, can be a solution for both > >> >> problems. When the page loads, freenet start fetching all the images, > >> >> and the browser gets the progress with 1 permanent connection. There > >> >> can be an image eg. "Image is loading...10%" and after some progress > >> >> change to 20% and so on, and when finishes downloading, it shows or > >> >> says eg. "Image finished loading, click to display". If it's done, we > >> >> don't need continuations anymore. Ofc it would need javascript to be > >> >> enabled. > >> >> > >> >> What you think? > >> > > >> > I filed a bug on that regarding activelinks, containing one possible way > >> > to > >> > solve it via javascript: > >> > > >> > https://bugs.freenetproject.org/view.php?id=3207 > >> > > >> > So when you implement it, please also do it for activelinks, as they are > >> > nice > >> > to have and could be re-enabled then. > >> > > >> > xor > > > > _______________________________________________ > > Devl mailing list > > Devl@freenetproject.org > > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl > > > _______________________________________________ > Devl mailing list > Devl@freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl > >
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
