This might be a good idea, and not hard to do. If yum wants bytes 2 through 300,000, download the file, without byte-ranges, and end the connection after you receive 300,000. Then perform the byte-range on result. Actually, we might be able to have the best of both worlds. Yum might even be able to send the byte-ranged request itself as you do know, but just have some logic that ends the connection after/if yum starts to receive more than it asked for. This way, if byte-ranged work, great. If they don't, we would get the whole file (the problem that I'm seeing sometimes at work now), except that we close the connection and yum still gets what it needs with byte-ranging the local result. Is this a good yum 2.3 feature request, or am I just dreaming? Joshua On Tue, Jun 14, 2005 at 10:35:04AM -0700, Michael Stenner wrote: > ... must support byteranges". urlgrabber does byteranges for local > files pretty reliably, so it would not actually be that hard to: > > a) download the whole file > b) fetch the byterange from the local file > > That's obviously very very painful. > > There are a couple of other options. One could do a stupid byterange > implementation in which you start downloading the whole file and then > stop when you get the part you're interested in. That's a bit > hackish, but not all that different from how we do byteranges in ftp > (except we use reget to start in the right place). > > This is getting strange enough that it's probably not the sort of > thing that should go in urlgrabber. It can be implemented outside of > urlgrabber with grabber.urlopen() > > -Michael > -- > Michael D. Stenner mstenner@xxxxxxxxxxxxxxx > ECE Department, the University of Arizona 520-626-1619 > 1230 E. Speedway Blvd., Tucson, AZ 85721-0104 ECE 524G > _______________________________________________ > Yum-devel mailing list > Yum-devel@xxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum-devel -- Joshua Jensen joshua@xxxxxxxx "If God didn't want us to eat animals, why did he make them out of meat?"
