Real-Time Streaming Systems (WebRTC + Live Data) · 课时

同步 WebRTC 元数据

学习使用实时数据通道（例如 WebSockets）在 WebRTC 通话期间同步非媒体相关元数据的策略。

第 1 / 4 课11 个步骤

同步 WebRTC 元数据 是 CoddyKit 上的免费 Real-Time Streaming Systems (WebRTC + Live Data) 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Real-Time Streaming Systems (WebRTC + Live Data) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Real-Time Streaming Systems (WebRTC + Live Data) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

What is WebRTC Metadata?

When you think of a WebRTC call, you likely picture audio and video. But what about all the other information that makes a call useful? This is where metadata comes in.

Metadata is "data about data." In WebRTC, it's all the non-media information that enhances your real-time experience, like user names, statuses, or shared application states.

Why Metadata Sync Matters

Synchronizing metadata is crucial for creating rich, interactive real-time applications. It allows you to:

Show who's currently speaking
Display user names and avatars
Share call status (e.g., "on hold", "recording")
Enable real-time collaboration features

Without it, a call is just raw audio/video with little context.

WebRTC Core: Media, Not Metadata

WebRTC is excellent at establishing direct peer-to-peer connections for audio, video, and even raw data (via RTCDataChannel). However, its primary signaling mechanism (for SDP/ICE exchange) is designed for connection setup, not continuous metadata exchange.

For broader application state or centralized updates beyond the initial handshake, we need a different approach.

A Dedicated Channel for Live Data

To handle metadata efficiently and flexibly, we often use a separate live data channel that runs alongside our WebRTC connections. This channel typically connects clients to a central server.

A popular choice for this is WebSockets, offering a persistent, bidirectional connection between client and server.

WebSockets + WebRTC: A Powerful Duo

Think of it this way:

WebRTC: Handles the direct, peer-to-peer flow of audio, video, and specific data streams between participants.
WebSockets: Manages the centralized, client-to-server-to-client exchange of metadata, like user status, shared pointers, or participant lists.

They work together to build a complete real-time experience.

Client-Side WebSocket Connection

On the client-side (your browser), connecting to a WebSocket server is straightforward using JavaScript. You create a new WebSocket object and define event handlers for when the connection opens, receives messages, or closes.

Try running this example in a browser's developer console:

<!DOCTYPE html>
<html>
<head>
  <title>WebSocket Connect</title>
</head>
<body>
  <h1>WebSocket Client</h1>
  <p>Check console for messages.</p>
  <script>
    // Using a public echo server for demo purposes
    const socket = new WebSocket('wss://echo.websocket.events');

    socket.onopen = (event) => {
      console.log('WebSocket connected!', event);
      socket.send('Hello from CoddyKit!');
    };

    socket.onmessage = (event) => {
      console.log('Message from server:', event.data);
    };

    socket.onclose = (event) => {
      console.log('WebSocket disconnected:', event);
    };

    socket.onerror = (error) => {
      console.error('WebSocket error:', error);
    };
  </script>
</body>
</html>

Sending Metadata via WebSocket

Once connected, sending metadata is as simple as calling the send() method on your WebSocket object. It's common practice to send data as JSON strings to easily structure your metadata.

This allows you to update other clients about your status, actions, or any relevant information.

<!DOCTYPE html>
<html>
<head>
  <title>Send Metadata</title>
</head>
<body>
  <h1>Send Metadata Example</h1>
  <p>Check console for sent messages.</p>
  <script>
    const socket = new WebSocket('wss://echo.websocket.events');

    socket.onopen = () => {
      console.log('WebSocket connected!');
      
      // Example: Sending a user status update
      const statusUpdate = {
        type: 'userStatus',
        userId: 'alice123',
        status: 'online',
        timestamp: new Date().toISOString()
      };
      socket.send(JSON.stringify(statusUpdate));
      console.log('Sent status update:', statusUpdate);

      // Example: Sending a "typing" indicator
      const typingIndicator = {
        type: 'typing',
        userId: 'alice123',
        isTyping: true
      };
      socket.send(JSON.stringify(typingIndicator));
      console.log('Sent typing indicator:', typingIndicator);
    };

    socket.onmessage = (event) => {
      console.log('Received (echoed) message:', event.data);
    };

    socket.onerror = (error) => console.error('WebSocket error:', error);
    socket.onclose = () => console.log('WebSocket disconnected.');
  </script>
</body>
</html>

Receiving and Handling Metadata

To receive metadata, you listen to the onmessage event. The received event.data will contain the message from the server. If you sent JSON, remember to parse it back into a JavaScript object.

Your application can then react to these updates, like showing a new participant in a list or displaying a "typing..." indicator.

<!DOCTYPE html>
<html>
<head>
  <title>Receive Metadata</title>
</head>
<body>
  <h1>Receive Metadata Example</h1>
  <p>Open console. Messages will appear when simulated.</p>
  <script>
    // This example uses a mock message source to simulate incoming data.
    // In a real app, 'socket' would be connected to an actual WebSocket server.
    const mockSocket = {
      onmessage: null,
      simulateMessage: function(data) {
        if (this.onmessage) {
          console.log("Simulating message:", data);
          this.onmessage({ data: JSON.stringify(data) });
        }
      }
    };

    // This is how your app would typically handle messages from a real WebSocket
    mockSocket.onmessage = (event) => {
      const receivedData = JSON.parse(event.data);
      console.log('Received metadata:', receivedData);

      if (receivedData.type === 'userStatus') {
        console.log(`User ${receivedData.userId} is now ${receivedData.status}.`);
      } else if (receivedData.type === 'typing') {
        console.log(`${receivedData.userId} is ${receivedData.isTyping ? 'typing...' : 'not typing.'}`);
      }
      // You would update your UI here based on 'receivedData'
    };

    // Simulate some incoming messages after a delay
    setTimeout(() => {
      mockSocket.simulateMessage({ type: 'userStatus', userId: 'bob456', status: 'online' });
    }, 1000);
    setTimeout(() => {
      mockSocket.simulateMessage({ type: 'typing', userId: 'bob456', isTyping: true });
    }, 2000);
    setTimeout(() => {
      mockSocket.simulateMessage({ type: 'typing', userId: 'bob456', isTyping: false });
    }, 3000);
  </script>
</body>
</html>

Example: Synchronizing Participant Lists

Imagine a video call with multiple participants. When someone joins or leaves, how do all other clients know?

A WebSocket server can manage the central list of active participants. When a user connects or disconnects (e.g., via their WebRTC signaling or a dedicated WebSocket message), the server updates its list and then broadcasts the new list to all active clients via their WebSocket connections.

Check Your Understanding

Which of the following is the primary role of a WebSocket connection when synchronizing metadata alongside a WebRTC call?

在交互式课程中回答

Recap: Metadata Sync with WebSockets

In this lesson, we explored the critical role of metadata synchronization in WebRTC applications. We learned that while WebRTC excels at media, a separate live data channel, often implemented with WebSockets, is ideal for managing non-media related information like user statuses or participant lists.

This combination creates richer, more interactive real-time experiences. Next, we'll dive deeper into building real-time chat features using WebRTC Data Channels!

免费开始

用 AI 导师学习 Real-Time Streaming Systems (WebRTC + Live Data) — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 12
课程: 48

免费开始学习查看完整课程

常见问题解答

「同步 WebRTC 元数据」课时是免费的吗？

是的 — 「同步 WebRTC 元数据」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Real-Time Streaming Systems (WebRTC + Live Data) 课程的其余内容，请升级到 CoddyKit PRO。 Real-Time Streaming Systems (WebRTC + Live Data) 课程共包含 4 节课。

「同步 WebRTC 元数据」这节课中我会学到什么？

学习使用实时数据通道（例如 WebSockets）在 WebRTC 通话期间同步非媒体相关元数据的策略。你通过在浏览器中直接运行的动手代码来练习 Real-Time Streaming Systems (WebRTC + Live Data)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Real-Time Streaming Systems (WebRTC + Live Data) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Real-Time Streaming Systems (WebRTC + Live Data) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「同步 WebRTC 元数据」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Real-Time Streaming Systems (WebRTC + Live Data) 课中编写并运行代码吗？

能。每节 Real-Time Streaming Systems (WebRTC + Live Data) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Real-Time Streaming Systems (WebRTC + Live Data)