* Update README.md
update link what pointed to publish_index.html
* fix read_index.html too
---------
Co-authored-by: aler9 <46489434+aler9@users.noreply.github.com>
@ -416,7 +416,7 @@ This web page can be embedded into another web page by using an iframe:
@@ -416,7 +416,7 @@ This web page can be embedded into another web page by using an iframe:
For more advanced setups, you can create and serve a custom web page by starting from the [source code of the publish page](internal/core/servers/webrtc/publish_index.html).
For more advanced setups, you can create and serve a custom web page by starting from the [source code of the publish page](internal/servers/webrtc/publish_index.html).
### By device
@ -804,7 +804,7 @@ This web page can be embedded into another web page by using an iframe:
@@ -804,7 +804,7 @@ This web page can be embedded into another web page by using an iframe:
For more advanced setups, you can create and serve a custom web page by starting from the [source code of the read page](internal/core/servers/webrtc/read_index.html).
For more advanced setups, you can create and serve a custom web page by starting from the [source code of the read page](internal/servers/webrtc/read_index.html).
Web browsers can also read a stream with the [HLS protocol](#hls). Latency is higher but there are less problems related to connectivity between server and clients, furthermore the server load can be balanced by using a common HTTP CDN (like CloudFront or Cloudflare), and this allows to handle readers in the order of millions. Visit the web page: