here are my very rough ideas for Metalink in HTTP headers http://www.ietf.org/id/draft-bryan-metalinkhttp-00.txt
briefly, it's: Link: <http://www2.example.com/example.ext>; rel="alternate"; Link: <ftp://ftp.example.com/example.ext>; rel="alternate"; Link: <http://example.com/example.ext.torrent>; rel="describedby"; type="torrent"; Link: <http://example.com/example.ext.asc>; rel="describedby"; type="application/pgp-signature"; Digest: SHA=thvDyvhfIqlvFe+A9MYgxAfm1q5= On Jul 28, 5:37 pm, Anthony Bryan <[email protected]> wrote: > this is similar to some of metalink's features, but done in HTTP headers. > > ---------- Forwarded message ---------- > From: Henrik Nordstrom <[email protected]> > Date: Mon, Jul 27, 2009 at 11:03 AM > Subject: Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors > To: HTTP Working Group <[email protected]> > > This draft made a bit of surprise appearance in the transport area > meeting today: > > http://tools.ietf.org/html/draft-ford-http-multi-server > > My initial reaction is lots of obvious overlap with other work and > misunderstandings of basic HTTP functions like ETag. > > Basic motivation behind the work may be reasonable however. > > I will try to catch the author for a more in-depth discussion shortly. > > Other opinions? > > Regards > Henrik > > -- > (( 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 -~----------~----~----~----~------~----~------~--~---
