webrtc - 为什么有 WebRTC 时我们需要 crossbar.io (WAMP)？

Question

据我了解，crossbar 提供了客户端之间的透明连接。因此客户端可以相互通信。WebRTC 做几乎相同的事情，没有具有较低延迟的中央服务器（除了信令服务器）。

那么为什么我们首先需要横杆呢？

我错过了什么吗？

标签： webrtccrossbar

Answer 1

The two technologies are very different from one another.

WebRTC enables voice, video and data to be passed in real time directly between browsers. It has no notion of messaging, signaling or even a network architecture. It is a kind of a building block that got implemented inside a web browser and you can now use. When using it, you'll still be needing servers to get one browser/device connected to another browser/device - a signaling server.

From looking at the site of crossbar.io, it seems like this is an open source framework that implements signaling for IOT devices - it can connect devices to a centralized server that handles the control messages and signals that get sent between the devices and/or users.

Here's the interesting thing - if Crossbar were to handle voice/video or low latency data transmission - they'd probably end up integrating WebRTC. And on the other hand, you can use Crossbar as a signaling mechanism for WebRTC.

Apples to oranges.