Edward Lee wrote: > Link Fingerprints are intended for complete file downloads, but many > download managers like DownThemAll request multiple chunks in parallel > to increase throughput. The problem is what should be done with these > partial Range requests for URIs that have a Link Fingerprint?
The answer is to not implement Link Fingerprints at the network layer :-) > (2) forces download managers to be aware of Link Fingerprints. If they > don't realize there's a concept of Link Fingerprints, transfers will > mysteriously fail when doing Range requests. This means they need to > explicitly remove the #fragment-id before requesting the transfer, but > because of this, they make the active decision to either support Link > Fingerprints by implementing it or choose not to compute the hash. Addons have to deal with all sorts of updates and changes to Firefox. I don't see this as any different. > Enforcing Link Fingerprints provides additional functionality in that > Range requests can be Link Fingerprinted. This means assuming the hash > of the specific range is known, the network channel can automatically > compute the hash to ensure it was transferred correctly. I don't understand what you mean by this. Are you suggesting the download manager could create an "artificial" link fingerprint for a Range to pass to the network layer? What would be the point? Gerv _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
