2009/6/23 Tatsuhiro <[email protected]>:
>
> On 6月22日, 午前5:59, Anthony Bryan <[email protected]> wrote:
>> On Wed, Jun 17, 2009 at 7:45 AM, Tatsuhiro <[email protected]> wrote:
>>
>> > On Jun 15, 6:24 am, Anthony Bryan <[email protected]> wrote:
>> > > from what I remember when this came up before, the filename in a
>> > > multi-file torrent should match the filename in the metalink (here
>> > > <file name="example.file">). I know this isn't too flexible but I
>> > > think it can be made to work for most cases now.
>>
>> > > Tatsuhiro, any ideas for improvements? perhaps a file or files
>> > > attribute for bittorrent URLs?
>>
>> > Yeah, if all file under files element matches to the content of
>> > torrent file, adding torrent attribute to files element might make
>> > things clear. But that seems very torrent specific.
>> > Personally, I don't like the way of multi-file torrent which treats
>> > many files as a single and hashing it into pieces. As said earlier in
>> > this thread, it requires that to checking a piece hash, more than 1
>> > file is needed sometimes. It makes things unnecessarily complicated.
>>
>> here's what I think would work:
>>
>> 1) use a single file torrent.
>>
>> 2) the filename in a multi-file torrent should match the filename in
>> the metalink (here <file name="example.file">).
>>
>> 3) add a file attribute to <url>s of type="bittorrent" so you can
>> select one file out of a multi-file torrent
>>
>> <url type="bittorrent" file="Fedora-11-i386-disc1.iso"
>> preference="100">http://torrent.fedoraproject.org/torrents//Fedora-11-i386-CDs.torrent</url>
>>
>
> If many files are listed in this way, same torrent URL is scattered in
> metalink file and
> this also requires an extra work for BitTorrent capable client: The
> client has to look url element under every file element and gather
> files which have same torrent file , because usually multi file
> torrent is handled in the one torrent session.

you mean a torrent capable client needs to go through the metalink &
grab all files in a mult-file torrent all at once?

I guess file="" isn't the best solution for all cases, but I'm having
trouble coming up with a better one for our paradigm of alternate URLs
for unique files. if we have another <metadata>/<torrent> section
under <files> (not <file)? I don't think that fits in with how we're
doing things tho.

let's keep thinking about/discussing this...

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to