Scott G. Miller writes: >Not a bad idea. I'm not sure that the way you notify of diminished shares >existing is necessarily a good one, but the idea of dropping large files >in this way isn't bad. Also, it may not be as effective when we have file >splitting. > >But assuming we did something like this, it might be a better idea to have >the nodes report what shares they have of a file when you have a failed >request. So as the RequestFailed propogates backwards, each node reports >what share it has. Each node receiving a list like this adds his/her own >shares to the list (eliminating duplicates). Two possibilities then >occur: > >1) The user can get this list and attempt to request each individual share >as its own key (enough shares to reconstruct that is) > >2) When any node on the chain sees enough parts to do this, it >automatically spawns the inserts and is responsible for reconstructing >before passing the whole document back down the chain. This has the >advantage of reintroducing the whole file into the network, rather than >having files make a progression from whole to split to dead with no >possibility of going the other way. > > Scott
Mmm. I like your method better than mine. I always intended that files should have the potential of rising from the dead and becoming whole files on freenet again, but I envisioned that happening at the destination node, or maybe that the nodes along the chain should watch as shares go by and reconstruct as they can. I thought it would be better to send back the shares instead of messages that they are available, in order to cut down on requests and speed things up. But that increases net-traffic, and is counter to the way things are done on freenet. So yes, your (second) plan is probably the best way to go. What really motivated me to look at this was the discussion about DOS attacks by repeated requesting, not so much saving disk space on freenet. While the fact that freenet is so space-inefficient still bothers me, the real motivation was more to make it that much harder for files to get squeezed out of freenet. Sigh. But this is an open-source project. Which means if I want this done, I should do it myself and submit it. But I really haven't read through the freenet code, I don't know how the whole thing works in detail, and who knows if I'll be able to follow through? Well, I can take a look, and maybe someone else out there is interested in helping out? ~mark _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
