Anthony Bryan wrote: > On Mon, Sep 28, 2009 at 3:05 AM, Neil M. > <[email protected]> wrote: >> >> Comments on draft 16 if its not too late in the process. None of these >> are a big deal, but here it goes. >> >> 4.2.9. The "metalink:logo" Element >> >> Add an option to base64 encode the logo file. This allows for embedding >> the logo in the metalink file itself. Reference RFC 2397. This is >> already well established as it is part of HTML 4.01. > > that could be cool. I think it may be simpler to leave it as it is tho. > > I wonder how many download managers natively support base64? they can > all definitely grab an image file, which seems simpler.
Any KDE app that uses kioslaves (KGet is definitely one of them) would support it, because there is an ioslave for data: that transparently returns a file stream, just like for http or ftp. I would think KGet uses its own code for the real HTTP downloads to have more control over ranges, but ioslaves to get the .metalink itself and things like the logo (if it supports logos at all). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
