> Yeah, distributing over freenet is probably the best thing, albeit the > most work and the least reliable.
I don't think reinserting a few files and changing some CHKs in the code is much work, and if a node can't retrieve a few widely requested files, then it probably has shitty references, meaning that any new nodes created from it won't work anyway. > a) a list of CHKs for all the important files, in the source somewhere, > kept up to date by an ant target that needs a working node (and an fcp > client) Nah, the files to which you refer don't change very often, we can do the insertion manually. > b) keep the redistributibles in a fixed place e.g. in the store. Agreed. > c) have a request process start with the node to fetch them if they are > not available; it needs to have retries, but only a finite number of > them... or maybe it could just keep going on a single thread until it > gets the files... If it doesn't get them with a 25 htl request, it probably isn't going to get them at all - retrying over and over again risks flooding the network. > d) have a UI for it, to tell the user what it is doing, how far it has > got and how to fix the problem without fetching them from freenet. Have > the Distribution Servlet UI link to the autodownload UI. Agreed. This should be an Infolet. Ian. -- Ian Clarke ian@[freenetproject.org|locut.us|cematics.com] Latest Project http://cematics.com/kanzi Personal Homepage http://locut.us/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20021114/08d546d0/attachment.pgp>
