kurento的WebRtcEndpoint和RtpEndpoint的基本区别
Basic difference between kurento's WebRtcEndpoint and RtpEndpoint
我在 kurento 的 java 文档 webrtcendpoint and rtpendpoint 中读到了这两者。但它们都表明它们以非常相似的方式发挥作用。两者都可以作为要约者和受约者来交换媒体。
我还提到了类似的 ，其中显示了两者的用法。
但无法得到明显的区别。
显式创建两者的必要性是什么？
两者的典型用例场景是什么。将不胜感激。
WebRtcEndpoint是WebRTC规范的实现。来自 this 草稿
The RTP framework comprises the RTP data transfer protocol, the RTP
control protocol, and numerous RTP payload formats, profiles, and
extensions. This range of add-ons has allowed RTP to meet various
needs that were not envisaged by the original protocol designers, and
to support many new media encodings, but raises the question of what
extensions are to be supported by new implementations. The development
of the WebRTC framework provides an opportunity to review the
available RTP features and extensions, and to define a common baseline
RTP feature set for all WebRTC Endpoints. This builds on the past 20
years of RTP development to mandate the use of extensions that have
shown widespread utility, while still remaining compatible with the
wide installed base of RTP implementations where possible.
RTP and RTCP extensions that are not discussed in this document can be
implemented by WebRTC Endpoints if they are beneficial for new use
cases. However, they are not necessary to address the WebRTC use
cases and requirements identified in [RFC7478].
基本上，WebRTC 是 RTP，其他东西建立在它之上。它专注于浏览器的实时通信。一方面，使用其中一种取决于您是否需要浏览器客户端。
我在 kurento 的 java 文档 webrtcendpoint and rtpendpoint 中读到了这两者。但它们都表明它们以非常相似的方式发挥作用。两者都可以作为要约者和受约者来交换媒体。
我还提到了类似的
显式创建两者的必要性是什么？ 两者的典型用例场景是什么。将不胜感激。
WebRtcEndpoint是WebRTC规范的实现。来自 this 草稿
The RTP framework comprises the RTP data transfer protocol, the RTP control protocol, and numerous RTP payload formats, profiles, and extensions. This range of add-ons has allowed RTP to meet various needs that were not envisaged by the original protocol designers, and to support many new media encodings, but raises the question of what extensions are to be supported by new implementations. The development of the WebRTC framework provides an opportunity to review the available RTP features and extensions, and to define a common baseline RTP feature set for all WebRTC Endpoints. This builds on the past 20 years of RTP development to mandate the use of extensions that have shown widespread utility, while still remaining compatible with the wide installed base of RTP implementations where possible.
RTP and RTCP extensions that are not discussed in this document can be implemented by WebRTC Endpoints if they are beneficial for new use cases. However, they are not necessary to address the WebRTC use cases and requirements identified in [RFC7478].
基本上，WebRTC 是 RTP，其他东西建立在它之上。它专注于浏览器的实时通信。一方面，使用其中一种取决于您是否需要浏览器客户端。