KIO metadata: resume -> range-start, resume_until -> range-end.
Review Request #117508 - Created April 12, 2014 and submitted
KIO metadata: resume -> range-start, resume_until -> range-end. This is much more self-explanatory to people wanting to request a byte range, unrelated to anything like resuming an interrupted download.
Would it not make sense to put the compatibility stuff in KIO::Job::addMetaData, rather than the slaves? That way it should maintain compatibility on both the application and slave side (for slaves shipped outside KIO). Although I guess setMetaData dn mergeMetaData would need the same compat hacks... would that be too much of a performance/maintenance hit?