Quoting Scott Young <scottyoung at adelphia.net>: > I was thinking it would be better to do what other programs do for > partial downloads: .dat files. An in-place reconstruction of the file > could take place after enough data for each segment is downloaded. If > the user can tell Freenet where they want to store the file after it > isfile downloaded, the dat file could be constructed in the same place > so that the file doesn't need to be copied across partitions in the > end. The DAT file would also be able to store data that is deleted from > the node, so that the data store could actually be smaller than the size > of the SplitFile being downloaded. Resuming downloads would also be > quicker because FEC wouldn't have to be run on already-decoded segments > again.
Correct me if I'm wrong here. It seems that to download a file as multiple DAT files, written to the hard drive as they come in, the information would have to come through fproxy (if you're using a web browser) and go to the browser, which would then save it to the disk. This means that for a file that would take, say, four DAT files, I have to click "Save To..." four times. Is there some way to get around this? As it stands I can say "Save To..." once, come back eight or nine hours later and it's done. The idea is very good otherwise. And if some way to get around baby-sitting a download could be had... FYI: I'm getting throughputs of 10-15K on files of ~700M. I'm impressed. -todd _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
