|
|
|
|
|
by geocar
3255 days ago
|
|
I've written a WebRTC "server" that can establish such a connection (and also acts as it's own STUN/TURN server) and hand off sockets to a local process. WebRTC isn't very complicated. The hardest part is probably ICE, which basically involves each point telling eachother what they see, and potentially consulting a third party (STUN/TURN). I'd love to see more magic there, but once that's in-place, I don't see what's so hard about just using DataChannels. One idea might be to put signalling into HTTP headers, e.g. have the client and server introduce something like: ICE: sdp-desc...
and if so, allow WebRTC to skip the ICE negotiation step if speaking to the server. |
|