As a ignorant user, I think that's as a general principal, Freenet should try to be as browser agnostic as possible..
1) Firefox may not be the dominant browser down the line- Freenet shouldn't constantly chase the tale of different browsers. 2) Most users don't use Firefox currently. Most general web users still use IE or Safari, depending on what their PC shipped with. 3) Freenet is a server process, and optimization shouldn't suffer unless absolutely necessary over a network. 4) It's considered "impolite" to modify settings in programs that you didn't ship. You don't want Freenet to get a reputation as a invading your system. 5) I think there may be other ways to fix the problem. One of the way to get around the persistent connection limit is to connect to Freenet on multiple hostnames, or DNS addresses. For example, if Freenet is running on the local system, the URLS on the page could be given multiple ways. For example, if we had a page of activelinks, freenet could return them as: http://127.0.0.1/CHK/foo1.png http://127.0.0.1/CHK/foo2.png http://localhost/CHK/foo3.png http://localhost/CHK/foo3.png http://192.168.1.15/CHK/foo5.png http://0.0.0.0/CHK/foo5.png (Linux only) By varying the URL, you increase the number of connections to the max per browser, rather than the max per server. See: http://www.ajaxperformance.com/2006/12/18/circumventing-browser-connection-limits-for-fun-and-profit/ Matthew Toseland wrote: > Firefox is able to create profiles, and run two of them at once (at least my > iceweasel is). I propose that the browse freenet script creates a new firefox > profile called Freeet (if it doesn't already exist), creates a user.js > telling it to use a lot of connections, turn off javascript, etc (if > necessary), and then launch it. > > One big reason for Freenet being slow is that web browsers used to access it > use very few connections. By turning off persistent connections, we have > increased that from 2 to 8 connections for firefox, but freenet would work > better (due to its high latency) with more. This especially impacts the > performance of node when the user has just installed it. > > I have tried implementing inline-image-prefetching, but this does not seem to > help. It is likely that there are other bottlenecks e.g. poor initial > connections, and the node's not sending its own requests in preference to > those of others because of anonymity. However, IMHO the above should still > help. > > Is it possible to automatically create a firefox profile from a batch > file/shell script, and then add the settings we need? We cannot expect the > average user to tweak the settings in about:config, even if we detect that > they need to and tell them. > > ------------------------------------------------------------------------ > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
