boyska/radiomanifest-spec
1
0
Fork 0
Code Issues 2 Pull requests Releases Wiki Activity

fix syntax

Browse source
This commit is contained in:
boyska 2022-02-23 13:41:06 +01:00
parent 8576b212d1
commit e23590ddd2
1 changed files with 9 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
spec.asciidoc
View file

@ -257,9 +257,10 @@ wanted RadioManifest to be deployable as _"just a bunch of static files"_, as a
=== The `<streaming>` section overlaps too much with /streaminfo.json === === The `<streaming>` section overlaps too much with /streaminfo.json ===
Almost. While `/streaminfo.json` is clearly valuable data, we wanted to account for more usecases: 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
* 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. 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 * 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 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 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 your usecase. Or, it may let the user explicitly select "low quality, low bandwidth" for users that want to