3 ms·
You first stated that these concepts are hard, which is really not the case. Many more terminology is really good explained here: https://webrtcglossary.com/ ht
by tpetry 6y ago
You first stated that these concepts are hard, which is really not the case. Many more terminology is really good explained here: https://webrtcglossary.com/ https://webrtcglossary.com/
Not understanding the byte protocol is understandable but a quite different topic. You really don't need to understand it, there are libraries for many programming languages doing the hard work for you. And if you want to understand it, it's normal you have to read a lot of different documents. If you would have no understanding of HTTP/2 you would have to read a lot of RFCs too as every version is built on the former version with retaining many of it's concepts
- im3w1l 6y ago> You first stated that these concepts are hard, which is really not the case. That was another person, I don't struggle with that. > If you would have no understanding of HTTP/2 you would have to read a lot of RFCs too as every version is built on the former version with retaining many of it's concepts The turd doesn't smell less because you managed to find another. The reason I wanted to read about it was because some sources say STUN requires two public IPV4. I wanted to know what would happen if I had only one. Or if I had two IPV6.