Damn! I though I have 1.8.0 on this node, so I did not check that against trunk sources. I'm sorry.
You are right, ranges on 1.8.0 works perfectly. Marek On Wed, Oct 20, 2010 at 5:18 PM, Brian Warner <[email protected]> wrote: > On 10/20/10 5:53 AM, slush wrote: > > Hi, > > > > I found that TahoeLAFS solves support for "Range" header with > > downloading whole file from grid and then returning a subset of original > > file. Is that because downloading just of small piece of file is > > impossible in Tahoe by it's design or just because nobody > > ask/implemented partial downloads from grid better? > > This was fixed in 1.8.0 (at least for immutable files) by my > "new-downloader" project. The new code only downloads the segments > (typically 128KiB each) that overlap the range you requested. > > Tahoe's file-encoding scheme was specifically designed to make it > efficient to download individual segments with minimal overhead (about > 0.5%, if I remember rightly), but up until 1.8.0, we hadn't gotten > around to taking advantage of it. > > cheers, > -Brian > > _______________________________________________ > tahoe-dev mailing list > [email protected] > http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev >
_______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
