https://github.com/otalk/rtcpeerconnection-jingle

rtcpeerconnection, extended with a JSON format. And easy to map to Jingle
https://github.com/otalk/rtcpeerconnection-jingle

Last synced: 2 days ago
JSON representation

rtcpeerconnection, extended with a JSON format. And easy to map to Jingle

• Host: GitHub
• URL: https://github.com/otalk/rtcpeerconnection-jingle
• Owner: otalk
• Created: 2018-04-07T17:59:31.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2022-12-08T08:53:18.000Z (almost 2 years ago)
• Last Synced: 2024-11-04T19:42:12.020Z (8 days ago)
• Language: JavaScript
• Homepage:
• Size: 688 KB
• Stars: 3
• Watchers: 8
• Forks: 3
• Open Issues: 15
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# RTCPeerConnection & Jingle

This module extends the RTCPeerConnection API to emit and process data in a JSON

format instead of SDP.

To use it, create your RTCPeerConnection with

```

const pc = new RTCPeerConnection({sdpSemantics: 'json'});

```

The `createOffer` and `createAnswer` methods will add a JSON field to the

RTCSessionDescription while the `setRemoteDescription` method processes

this field and transforms it to SDP.

The transformation is done using the [sdp](https://github.com/otalk/sdp) module and reensembles

the data structures used by the [ORTC-WebRTC shim](https://github.com/otalk/rtcpeerconnection-shim).

This format can easily be transformed to the Jingle format used by [jxt](https://github.com/otalk/jxt),

allowing the use of Jingle for signaling.

This package superceedes the older [RTCPeerConnection package](https://www.npmjs.com/package/rtcpeerconnection). Wrapping the native RTCPeerConnection API in a nice wrapper was necessary in 2013 but is no longer required these days.