Timm Murray: > > > Yes, in fact if you hang around long enough, you will find a > > > lot of people suggesting using Freenet to overcome the > > > Slashdot Effect. Freenet is still slower then HTTP in the > > > sense that it will use more bandwidth. An HTTP server under > > > normal bandwidth load will allways be faster then Freenet, but > > > Freenet is infinatly faster then not being able to get the > > > document at all.
Splitfiles make Freenet faster than any webserver - the bandwidth attainable should be limited by the size of the network and average node throughput. > > Would it be possible to add FreeNet into something like Squid so > > that any web browser inside a LAN that is already set to use our > > Squid proxy server would be able to request FreeNet objects > > without needing to run nodes on every machine or to configure > > each machine to use a special FreeNet proxy? It'd seem to me > > that'd be a major issue on making it available inside firewalls > > and such. Assuming that is even a desired goal for FreeNet. Yes. > Every computer should be running a Freenet node anyway. There are > ways to make Freenet work behind firewalls, though it's a bit > tricky last I heard. Something like a Squid proxy server for > Freenet is actualy redundant. That's ridiculous. Run _one_ node per LAN. _______________________________________________ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
