I just implemented initial ml4 support: * Parser (ml3 parser also present; version detected per document) * Transparent-Content-Negotiation support (TCN) * Accepting application/metalink4+xml (q=0.9) and application/metalink +xml (q=0.8) * .meta4 as recognized file extension
(Still) not supported: * no ml4 export (still uses ml3) * chunked hashes * signatures * any non-http/non-ftp sources * only the last ml4:hash will be taken into account * only the first ml4:os and ml4:language per file will be taken into account I tested against the complex demo meta4 from the spec, mirrorbrain (go- oo metalinks via TCN) and some custom metalinks. The UI is the same for ml3 and ml4. It should be safe to change the export functionality to use ml4, shouldn't it? Please give it a try and report any issues back at: http://bugs.code.downthemall.net/trac/ticket/1510 To test use the nightly builds: http://bugs.code.downthemall.net/trac/wiki/NightlyBuilds Some implementation details: * DownThemAll uses a "preference" scale of 1 - 200, higher = better. This worked well with ml3. In ml4 the priority value is first prioritized (min(ml4:priority / 4, 1) according to ml4:location == browser:locale and then scaled into [1, 100] * The parser implementation was derived from the ml3 implementation. I left some stuff in that is no longer in ml4, such as license/ copyright. This shouldn't be a problem * There is already infrastructure to store partial/chunked hashes. However I need to implement parsing and also partial hash computation. * application/metalink4+xml;q=0.9 and application/ metalink4+xml;q=0.8 ;) Cheers Nils -- 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.
