A lot of the problem actually is due to users running nodes with old config files generated by the windows configurator, which forces all settings (doesn't write %'s), so they run with old settings such as 50 node routing tables, which mean that the unix nodes run a lot better than the windows ones, but even the unix nodes don't run well because the network is stuffed with windows nodes with stupid configs. Ian recently appealed for a maintainer for the windows config utilities... I suppose I will have to do it if nobody comes forward, but if you can do it, please contact him. The software in question is written in C. A longer term solution would be to handle configuration in the node via HTML, but *this will take considerable effort and time*.
On Mon, Mar 08, 2004 at 10:33:43AM -0500, vinyl1 wrote: > I would imagine that the problem is a lot of users running nodes with older, > incompatible releases. If part of the content is only stored on such nodes, the > chance of a user with the new release being able to retrieve is very slim. If > everyone was up to date, I don't think there would be a problem. > > A good test would be to insert new content through an up-to-date node. Other users > using up-to-date nodes should be able to retrieve it quickly. > > I agree, there should be a way to notify users of older releases that they should > update their nodes. Perhaps a broadcast feature? Or maybe auto-update through > Freenet itself? -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ 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]
