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.

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

WebRTC refactor. data channels, STUN/TURN support. #28964

Merged
merged 1 commit into from May 21, 2019

Commits on May 16, 2019

  1. WebRTC refactor. Data channels, STUN/TURN support.

    A big refactor to the WebRTC module. API is now considered quite stable.
    
    Highlights:
    
    - Renamed `WebRTCPeer` to `WebRTCPeerConnection`.
    - `WebRTCPeerConnection` no longer act as `PacketPeer`, it only handle the connection itself (a bit like `TCP_Server`)
    - Added new `WebRTCDataChannel` class which inherits from `PacketPeer` to handle data transfer.
    - Add `WebRTCPeerConnection.initialize` method to create a new connection with the desired configuration provided as dictionary ([see MDN docs](https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/RTCPeerConnection#RTCConfiguration_dictionary)).
    - Add `WebRTCPeerConnection.create_data_channel` method to create a data channel for the given connection. The connection must be in `STATE_NEW` as specified by the standard ([see MDN docs for options](https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/createDataChannel#RTCDataChannelInit_dictionary)).
    - Add a `data_channel_received` signal to `WebRTCPeerConnection` for in-band (not negotiated) channels.
    - Renamed `WebRTCPeerConnection` `offer_created` signal to `session_description_created`.
    - Renamed `WebRTCPeerConnection` `new_ice_candidate` signal to `ice_candidate_created`
    Faless committed May 16, 2019
    Copy the full SHA
    729b1e9 View commit details
    Browse the repository at this point in the history