How to validate WebRTC connection signals when peers can't trust each other? -


i building webrtc app 2 users selected @ random , connect each other chat. both clients keep open websocket connection , planning use exchange offers/answers signal connection. case trying account when there peer intentionally sends bad configuration information, , when peer might spontaneously disconnect in middle of signaling exchange.

my solution first case have server keep state of exchange, when connection first established expect user provide offer , user b have answer. appropriate? or should implemented exclusively client side?

my solution second problem feels me hack. trying notify user match has been made , user set timeout 20 seconds, if connection hasn't been made in amount of time should move on...

are these appropriate solutions? how reliably establish webrtc when either peer can't trusted? should signaling server concerned state of exchange?

sounds you're more concerned call set errors rather being able trust identity of remote peer. 2 different problems.

assuming call set errors concerned shouldn't trying avoid them should trying make sure application can handle them. network connection issues crop , need handled.

setting timer establishment of webrtc call complete logical solution. displaying warning user time limit approaching seems idea. sip signalling protocol , has defined timeout completion of transaction , if doesn't complete within time generate error response. use same approach.


Comments

Popular posts from this blog

Django REST Framework perform_create: You cannot call `.save()` after accessing `serializer.data` -

Why does Go error when trying to marshal this JSON? -