Toad wrote:
{many nice things}Thank you toad, a job well done!
Could you please cast your eye to the http interface.
What happens -- Has happend for ages.-- is that after a minimal amount of activity.
OR a modest amount of up time, http connection via fproxy are unresponsive.
This is very much like the max connection problems of the browsers which have been documented.
Fixes for Mozilla are also documented, and applied.
However I can browse with galeon, experience artic level slowdowns whilst talking to the local node (!!)
Then power up mozilla (user.prefs updated) and instantly have the same problems, talking to the local node.
Netstat will show maybe 30 or 40 connections open to fproxy
It's Dire. Its been around for a year, more I'm sure.
Regards
John Ps, the reward for good work is the chance to do more good work.
_______________________________________________ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
