webrtc-unreliable-client

Just enough hacks to connect a native client to a webrtc-unreliable server.

At first this was going to just wrap webrtc-rs, but I experienced absurd compile times going that route .. Knowing that I very likely needed a much smaller subset of functionality to get an unreliable, unordered datachannel set up to connect to a webrtc-unreliable server, I cloned all webrtc-rs and started to cut it down. I'm not so sure this was the correct path. Protocols like DTLS, SCTP, SDP really don't have a lot of fat to trim, so it seems. However, I believe this is progress.

If anyone knows of a good way to anayze during run-time which functions are never called, please get in touch!