I'm trying to understand common practice for including bittorrent URLs
in a metalink, either with version 3.0 or the IETF draft.
<file name="example.file">
<size>XXXX</size>
<verification>
<hash .../>
</verification>
<resources>
<url type="bittorrent">http://www.example.com/example.torrent</url>
</resources>
</file>
This makes sense, if each file has its own torrent. However, Fedora
and other torrent generator persons don't always do this. Instead,
they will have multiple files inside the torrent:
{'path': ['Fedora-10-x86_64-DVD.iso'], 'length': 4172283904L}
{'path': ['SHA1SUM'], 'length': 788}
In this instance, the metalink for the Fedora-10-x86_64-DVD.iso that
MirrorManager publishes has direct FTP/HTTP URLs to that ISO, and the
<verification> section has info on this single file.
But this single file isn't published in its own torrent, it's in a
torrent with those multiple pieces. The whole <verification> section
then is either meaningless, or would provide incorrect information, as
compared to the torrent URL.
Likewise, the CD downloads for the multi-CD set includes direct
HTTP/FTP URLs to each of the CDs, but the torrent includes all of them
in a single torrent.
Is the <verification> section completely ignored when torrents are
used, and instead the torrent metadata used? If so, can that be
documented in the specification?
Thanks,
Matt
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Metalink Discussion" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/metalink-discussion?hl=en
-~----------~----~----~----~------~----~------~--~---
