Michael Herger wrote:
I thought of this objection. But its one request, one file. HTML files typically cause further requests (images) which will result in several parallel transfers. But these are all independant requests.
All very true. But it is possible to generate multiple independent requests with one mouse click. As you point out, this happens with almost every web page you visit. Only one document is delivered in the initial request, but the handling application for that document type interprets it and issues additional requests for other items. Playlist handling for most streaming formats works in the same.
The servers can handle these requests just fine.
What's needed is a means for the user agent to conveniently generate these requests and then handle the resulting issues of picking a destination, possible bandwidth saturation and perhaps dealing with pause and restart issues. These features are usually bundled in a free standing application or browser extension known generically as a "download manager".
But I think bigjilm's situation can be improved without going to those lengths. I think all they need is for the download links to appear in the album songlist page, rather than the songinfo page. Still one click per track, but save a lot of paging around to get to those links.
--rt
_______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
