Juliusz Chroboczek <[EMAIL PROTECTED]> wrote: >> Do you think using another web proxy, which supports outgoing >> presistent connections, between WWWOFFLE and the Internet would help >> be and make browsing faster? > > It certainly would. Pipelining would help even more.
Thanks. I just installed polipo proxy (version 1.0.0-1 from Debian) as a parent to WWWOFFLE on my side of the LFN, and then another polipo proxy as a parent of that one on the public-Internet side of the LFN. On my side I use: clientTimeout = 30m On the Internet side I use: serverTimeout = 30m Is that a good idea? To have the TCP connections between the two polipo's presisente for half an hour, instead of the standard 2 minutes. > The simplest way to achieve that is to put an HTTP proxy between the > LFN and the Internet. (I do this regularly when browsing over lossy > Wifi links -- not quite LFNs, but they have similar issues --, and it > helps a lot.) Done that, see above. Any other options you can recomment to achive best results? > Of course, split-TCP will only make a difference if the TCP instance > over the LFN has enough time to grow its congestion windows -- and > unless your TCP/IP stack is doing black magic behind your back, it > means that the HTTP implementations on both ends of the LFN must > support persistent requests. What about using Hybla TCP instead of the standard one? net.ipv4.tcp_congestion_control=hybla Are you familiar with how this works? Does it have to be used on both sides of the link to work? -- Miernik http://miernik.name/
