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

Inform about more stats and connection errors #2

Open
thammi opened this issue Nov 23, 2014 · 0 comments
Open

Inform about more stats and connection errors #2

thammi opened this issue Nov 23, 2014 · 0 comments
Labels
palava-client signaltower

Comments

@thammi
Copy link
Member

thammi commented Nov 23, 2014

Issue by farao
Sunday Jan 19, 2014 at 23:45 GMT
Originally opened as palavatv/palava-client#3

In order to tell the user why a connection to a peer could not be established, more information sources need to be watched. The main one will probably be the getStats() function of the PeerConnection object.

It needs to be figured out which browsers support getStats and to which extent and which other webrtc-function can help with getting the state of a connection (e.g. as workarounds when getStats is not or not entirely supported).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
palava-client signaltower
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@janlelis @thammi