elm-allo | Videoconference WebRTC example with an Elm frontend | SDK library

by mpizenberg JavaScript Version: Current License: MPL-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | elm-allo Summary

elm-allo is a JavaScript library typically used in Utilities, SDK applications. elm-allo has no bugs, it has no vulnerabilities, it has a Weak Copyleft License and it has low support. You can download it from GitHub.

Videoconference WebRTC example with an Elm frontend. Requires https. More info in the post on Elm discourse.

Support

Quality

Security

License

Reuse

Support

elm-allo has a low active ecosystem.

It has 14 star(s) with 4 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

There are 2 open issues and 1 have been closed. On average issues are closed in 6 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of elm-allo is current.

Quality

elm-allo has 0 bugs and 0 code smells.

Security

elm-allo has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

elm-allo code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

elm-allo is licensed under the MPL-2.0 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

elm-allo releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 33 lines of code, 0 functions and 6 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed elm-allo and discovered the below as its top functions. This is intended to give you an instant insight into elm-allo implemented functionality, and help decide if they suit your requirements.

A shim for removing all streaming tracks .
Creates a new PeerConnection instance
Creates a WebRTC client .
Shims the current protocol size .
create adapter factory
Signal socket .
Shim a tracker receiver .
A wrapper around the Dtmender method used to modify the stream
Fetches fullscreen configuration .
This function is called when a message negotiation and sends it to the remoteDescription

Get all kandi verified functions for this library.

elm-allo Key Features

No Key Features are available at this moment for elm-allo.

elm-allo Examples and Code Snippets

No Code Snippets are available at this moment for elm-allo.

Community Discussions

Trending Discussions on elm-allo

WebRTC "perfect negotiation" issues

QUESTION

WebRTC "perfect negotiation" issues

Asked 2020-May-24 at 00:29

I have been trying to implement WebRTC "perfect negotiation" as explained in this blog post. Unfortunately, I'm very often triggering errors on the polite side of the conversation (in the following linked code, this is the last peer to join).

The two most frequent errors are InvalidStateError: Cannot rollback local description in stable caused by this line and ONN DOMException: "Cannot set local offer in state have-remote-offer" triggered here and caused by this line. That second error is quite inexplicable to me since the line before checks that we should be in stable state and it is the first async call following that.

If you want to try it for yourself, my code is hosted on GitHub. It can be deployed directly on Heroku:

...

ANSWER

Answered 2020-May-24 at 00:29

TL;DR: Browser bugs fixed in Firefox 77 & the spec, as well as a separate bug in Chrome.

ONN DOMException: "Cannot set local offer in state have-remote-offer" ... That second error is quite inexplicable to me since the line before checks that we should be in stable state and it is the first async call following that.

WebRTC negotiation code has the tricky task of translating synchronous signaling messages into asynchronous operations on the RTCPeerConnection object. To ensure order, these asynchronous methods are chained internally, so only one runs at a time, because state machine.

Under signaling stress, it's possible for this internal chain to fill up, which complicates things, because methods you invoke end up running later, not immediately in the state you just observed synchronously.

The "second error" happened because the browser erroneously fired the negotiationneeded event while the RTCPeerConnection object's internal operations chain was non-empty. The spec has now been fixed so this won't happen.

Since the browser controls when the negotiationneeded event is fired, this takes care of it.

InvalidStateError: Cannot rollback local description in stable

The "first error" on the impolite side is similarly a symptom of an overloaded chain: synchronous state check that we're NOT in stable, followed by this:

Source https://stackoverflow.com/questions/61956693

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install elm-allo

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: