Re:Untangling the WebRTC Flow
by api on Monday November 06, 2017 @06:57PM
(#15640055)
I've designed several p2p protocols. WebRTC is at least two orders of magnitude more complex than necessary. The same is true of all its component protocols.
It's typical of modern network protocols. They must be designed by committee. Web sockets is for a different use case but it's full of cruft as well. Why couldn't it just drop to TCP? But no there's cruft in there for SOAP for some insane reason. I guess someone from MS was on the committee.
Of course a lot of modern software is over-engineered so maybe it's just a general cancer.
It's typical of modern network protocols. They must be designed by committee. Web sockets is for a different use case but it's full of cruft as well. Why couldn't it just drop to TCP? But no there's cruft in there for SOAP for some insane reason. I guess someone from MS was on the committee.
Of course a lot of modern software is over-engineered so maybe it's just a general cancer.