The Internet as we know it was created on top of HTTP versions 1.0 and 1.1, with HTTP/1.1 being dominant for the last 20 years. The growing demand for new features and capabilities showed several cavities in it and they were addressed in HTTP/2, which has been developed and adopted as a successor for 1.1. You can read the Introduction to HTTP/2 by Google team to see what exactly HTTP/2 has to offer.
At the moment HTTP/2 is supported in all modern browsers and every time users are trying to reach some resource on the Internet, their browser tries to connect through this new protocol version. If it succeeds then all further collaboration is performed via this new channel. If HTTP/2 in unavailable then the browser switches to HTTP/1.1.
Softvelum team has implemented HTTP/2 for some of Nimble Streamer output HTTP-based protocols to provide our customers with one more advantage for their end-users and establish the ground for further development.
Nimble Streamer now has support for HTTP/2 protocol in most popular streaming scenarios. No change to input streams is required, you only need to enable the feature as described in "Enabling HTTP/2" section below.
HTTP Live Streaming (HLS) by Apple is a de-facto standard for end-user media consumption so we implemented extended support for HTTP/2:
MPEG-DASH live streams and VOD can be played via HTTP/2 in all use cases.
Nimble Steamer can serve progressive download over HTTP/2.
At the moment only aforementioned protocols can be delivered via HTTP/2.
Everything else - HTTP re-streaming, Icecast and HTTP MPEG-TS - will be processed only via HTTP/1.1. We'll add them later on.
HTTP/2 can be used only when Nimble Streamer streams over HTTPS, so in order to make it process HTTP/2 requests, you need to do the following.
After that you'll be able to use HTTP/2 to reach live streams with HLS and MPEG-DASH protocols enabled.
Nimble Streamer uses LS-HPACK library for encoding and decoding HTTP headers using HPACK compression mechanism.
Softvelum team would like to say thank you to LiteSpeed team, we appreciate their effort and technical expertise. We've made several contributions to LS-HPACK code base and we plan to continue that support as long as we move forward in our HTTP/2 development.
Let us know if you have any thoughts or feedback regarding HTTP/2-based streaming.
Nimble Streamer, Nimble Advertizer, HLS in Nimble Streamer, MPEG-DASH in Nimble Streamer
At the moment HTTP/2 is supported in all modern browsers and every time users are trying to reach some resource on the Internet, their browser tries to connect through this new protocol version. If it succeeds then all further collaboration is performed via this new channel. If HTTP/2 in unavailable then the browser switches to HTTP/1.1.
Softvelum team has implemented HTTP/2 for some of Nimble Streamer output HTTP-based protocols to provide our customers with one more advantage for their end-users and establish the ground for further development.
HTTP/2 in Nimble Streamer
Nimble Streamer now has support for HTTP/2 protocol in most popular streaming scenarios. No change to input streams is required, you only need to enable the feature as described in "Enabling HTTP/2" section below.
HLS
HTTP Live Streaming (HLS) by Apple is a de-facto standard for end-user media consumption so we implemented extended support for HTTP/2:
- Live HLS streams with fMP4/CMAF, MPEG-TS and audio-only containers are fully supported.
- Ads insertion in live HLS via Nimble Advertizer is working fine as usual.
- HLS DVR output works fine with all of its features.
- VOD HLS works with all of its features.
MPEG-DASH
MPEG-DASH live streams and VOD can be played via HTTP/2 in all use cases.
Progressive download
Nimble Steamer can serve progressive download over HTTP/2.
Other protocols
At the moment only aforementioned protocols can be delivered via HTTP/2.
Everything else - HTTP re-streaming, Icecast and HTTP MPEG-TS - will be processed only via HTTP/1.1. We'll add them later on.
Enabling HTTP/2
HTTP/2 can be used only when Nimble Streamer streams over HTTPS, so in order to make it process HTTP/2 requests, you need to do the following.
- Upgrade Nimble Streamer to the latest version or install it if you haven't done that yet;
- Set up SSL certificate for Nimble Streamer;
During the setup, add ssl_http2_enabled=true parameter.
After that you'll be able to use HTTP/2 to reach live streams with HLS and MPEG-DASH protocols enabled.
LiteSpeed HPACK library
Nimble Streamer uses LS-HPACK library for encoding and decoding HTTP headers using HPACK compression mechanism.
Softvelum team would like to say thank you to LiteSpeed team, we appreciate their effort and technical expertise. We've made several contributions to LS-HPACK code base and we plan to continue that support as long as we move forward in our HTTP/2 development.
Let us know if you have any thoughts or feedback regarding HTTP/2-based streaming.
Related documentation
Nimble Streamer, Nimble Advertizer, HLS in Nimble Streamer, MPEG-DASH in Nimble Streamer
No comments:
Post a Comment
If you face any specific issue or want to ask some question to our team,
PLEASE USE OUR HELPDESK
This will give much faster and precise response.
Thank you.
Note: Only a member of this blog may post a comment.