Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update FAQ about WebRTC #239

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update FAQ about WebRTC #239

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions about/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,13 +50,13 @@ The WebKit project provides a [features status page](https://webkit.org/status/)
The WPE project currently does not have an official list of the Web features it supports. It might provide one in the future, but for the time being, we recommend users check for specific features by testing WPE through the Cog browser.


## What's the status regarding WebRTC?
## What's the status regarding WebRTC?

As of March 2022 the facts are:

1. [WPEWebKit upstream has support for WebRTC](https://blogs.gnome.org/tsaunier/2018/07/31/webkitgtk-and-wpe-gains-webrtc-support-back/), by relying on [LibWebRTC](https://webrtc.googlesource.com/src/).
2. LibWebRTC is bundled as third-party library in WebKit's upstream repository.
3. The LibWebRTC backend doesn't support hardware-accelerated encoders and decoders.
3. The LibWebRTC backend supports hardware-acceleration only for decoding. Encoding is supported only via software encoders.
4. LibWebRTC bundles [BoringSSL](https://boringssl.googlesource.com/boringssl/), which is a fork of OpenSSL started while OpenSSL
was still under the dual OpenSSL and SSLeay licences.

Expand All @@ -67,7 +67,7 @@ Taking these facts into account, the WPEWebKit maintainers have decided to leave
- The lack of hardware-accelerated support in LibWebRTC would incur a bad
performance impact on the embedded platforms that WPE targets.

In order to solve these issues, an alternative WebRTC backend based on [GstWebRTC](http://blog.nirbheek.in/2018/02/gstreamer-webrtc.html) will be enabled by default in the WPE upstream CMake build, hopefully during 2023; bug [#235885](https://bugs.webkit.org/show_bug.cgi?id=235885) is being used to track progress. This new backend will seamlessly integrate with hardware-accelerated encoders and decoders on most embedded platforms. GstWebRTC depends on [OpenSSL](https://www.openssl.org/), which is released under an Apache-style license, so it doesn't have limitations regarding redistribution in binary form.
In order to solve these issues, an alternative WebRTC backend based on [GstWebRTC](http://blog.nirbheek.in/2018/02/gstreamer-webrtc.html) will be enabled by default in the WPE upstream CMake build, hopefully soon; bug [#235885](https://bugs.webkit.org/show_bug.cgi?id=235885) is being used to track progress. This new backend will seamlessly integrate with hardware-accelerated encoders and decoders on most embedded platforms. GstWebRTC depends on [OpenSSL](https://www.openssl.org/), which is released under an Apache-style license, so it doesn't have limitations regarding redistribution in binary form.


## What's up with EME? How can I support this feature in my WPE-based product?
Expand Down
Loading