From 8576b212d120b39f0f6684df5843c14a3852cb80 Mon Sep 17 00:00:00 2001 From: boyska Date: Wed, 23 Feb 2022 13:40:09 +0100 Subject: [PATCH] why --- spec.asciidoc | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/spec.asciidoc b/spec.asciidoc index c709fd7..5ab7c27 100644 --- a/spec.asciidoc +++ b/spec.asciidoc @@ -254,6 +254,18 @@ for years, so you don't even need a special software to keep it working. Of course, nothing prevents a CMS to generate this file dynamically, making this way simpler for users. But we wanted RadioManifest to be deployable as _"just a bunch of static files"_, as a way to increase early adoption. +=== The `` section overlaps too much with /streaminfo.json === + +Almost. While `/streaminfo.json` is clearly valuable data, we wanted to account for more usecases: + - A radio should be able to list more than one URL for streaming. This can be for load balancing reasons, for + example. M3U are a simple way to achieve this. + - A radio can (and probably should) have not only more URLs for streaming, but actually stream different + versions: different qualities, different codecs, etc. It is reasonable that, as a user, you don't really + care about all those details: «Just gimme the audio!». However, your client could select the best codec for + your usecase. Or, it may let the user explicitly select "low quality, low bandwidth" for users that want to + save bandwidth. This is possible with radiomanifest adding multiple `` elements, and is + unfortunately not with `/streaminfo.json` + == Meta