搜尋套件、儲存庫與 APP 分類

套件詳情v0.2.1

web_socket_client

一個簡單的 Dart WebSocket 客戶端,包含自動重連邏輯。

AndroidiOSWebmacOSWindowsLinux
近 30 天下載
8.9萬
喜歡數
216
Pub 分數
160

安裝套件

flutter pub add web_socket_client

套件介紹

根據套件公開資料產生的選型評估,僅供參考。

一個輕量級的 Dart WebSocket 客戶端,可實現客戶端與伺服器之間的即時通訊。它具備內建的自動重連邏輯,即使在網路中斷時也能確保連接穩定。設計簡潔且可靠,支援所有主要平台,包括 Android、iOS、Web、macOS、Windows 和 Linux。適用於需要持續雙向資料流的應用程式,例如即時聊天應用、即時更新或協作工具。

適用情境

  • 即時聊天應用
  • 即時資料流
  • 協作編輯工具
  • 物聯網設備通訊
  • 通知系統

主要特色

  • 自動重連
  • 跨平台支援
  • 簡單 API
  • 內建錯誤處理
  • 輕便高效

適合對象

  • 開發即時功能的開發者
  • 需要持久連接的應用程式
  • 跨多個平台的項目
  • 優先考慮連接穩定性的團隊

使用建議

  • 需要相容的 WebSocket 伺服器
  • 特定用例可能需要自定義重試邏輯
  • 僅限 WebSocket 協議
  • 不適合非即時通訊

原始 README

以下為關聯原始碼儲存庫的 README 原文快照,最新內容請造訪原始碼儲存庫。

WebSocket Client

build coverage pub package style: very good analysis License: MIT

A simple WebSocket client for Dart which includes automatic reconnection logic.

Quick Start 🚀

// Create a WebSocket client.
final socket = WebSocket(Uri.parse('ws://localhost:8080'));

// Listen to messages from the server.
socket.messages.listen((message) {
  // Handle incoming messages.
});

// Send a message to the server.
socket.send('ping');

// Close the connection.
socket.close();

Establishing a Connection 🔌

The WebSocket client will attempt to establish a connection immediately upon initialization. By default, a timeout will occur if establishing a connection exceeds 60 seconds but a custom timeout duration can be provided:

final uri = Uri.parse('ws://localhost:8080');

// Trigger a timeout if establishing a connection exceeds 10s.
final timeout = Duration(seconds: 10);
final socket = WebSocket(uri, timeout: timeout);

Reconnecting 🔄

If the WebSocket client is not able to establish a connection, it will automatically attempt to reconnect using the provided Backoff strategy. By default, a BinaryExponentialBackoff is used but a custom backoff can be provided.

There are three built-in backoff strategies but a custom backoff strategy can be written by implementing the Backoff interface.

ConstantBackoff

This backoff strategy will make the WebSocket client wait a constant amount of time between reconnection attempts.

// Wait a constant 1s between reconnection attempts.
// [1, 1, 1, ...]
const backoff = ConstantBackoff(Duration(seconds: 1));
final socket = WebSocket(uri, backoff: backoff);

LinearBackoff

This backoff strategy will make the WebSocket client wait a linearly increasing amount of time until an optional maximum duration is reached.

// Initially wait 0s and increase the wait time by 1s until a maximum of 5s is reached.
// [0, 1, 2, 3, 4, 5, 5, 5, ...]
const backoff = LinearBackoff(
  initial: Duration(seconds: 0),
  increment: Duration(seconds: 1),
  maximum: Duration(seconds: 5),
);
final socket = WebSocket(uri, backoff: backoff);

BinaryExponentialBackoff

This backoff strategy will make the WebSocket client wait an exponentially increasing amount of time until a maximum step is reached.

// Initially wait 1s and double the wait time until a maximum step of of 3 is reached.
// [1, 2, 4, 4, 4, ...]
const backoff = BinaryExponentialBackoff(
  initial: Duration(seconds: 1),
  maximumStep: 3
);
final socket = WebSocket(uri, backoff: backoff);

Monitoring the Connection ⚡️

The WebSocket client exposes a connection object which can be used to query the connection state at any given time as well as listen to real-time changes in the connection state.

final uri = Uri.parse('ws://localhost:8080');
final socket = WebSocket(uri);

// Listen to changes in the connection state.
socket.connection.listen((state) {
  // Handle changes in the connection state.
});

// Query the current connection state.
final connectionState = socket.connection.state;

The connection state can be one of the following:

  • connecting: the connection has not yet been established.
  • connected: the connection is established and communication is possible.
  • reconnecting: the connection was lost and is in the process of being re-established.
  • reconnected: the connection was lost and has been re-established.
  • disconnecting: the connection is going through the closing handshake or the close method has been invoked.
  • disconnected: the WebSocket connection has been closed or could not be established.

* The disconnected connection state contains nullable fields for the close code, close reason, error, and stack trace.

Sending Messages 📤

Once a WebSocket connection has been established, messages can be sent to the server via send:

final socket = WebSocket(Uri.parse('ws://localhost:8080'));

// Wait until a connection has been established.
await socket.connection.firstWhere((state) => state is Connected);

// Send a message to the server.
socket.send('ping');

Receiving Messages 📥

Listen for incoming messages from the server via the messages stream:

final socket = WebSocket(Uri.parse('ws://localhost:8080'));

// Listen for incoming messages.
socket.messages.listen((message) {
  // Handle the incoming message.
});

Protobuf 💬

If you're using web_socket_client on the web with Protobuf, you might want to use binaryType when initializing the WebSocket class. binaryType is only applicable on the web and is not used on desktop or mobile platforms.

final socket = WebSocket(Uri.parse('ws://localhost:8080'), binaryType: 'arraybuffer');

See https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/binaryType for more info.

Closing the Connection 🚫

Once a WebSocket connection is established, it will automatically attempt to reconnect if the connection is disrupted. Calling close() will update the connection state to disconnecting, perform the closing handshake, and set the state to disconnected. At this point, the WebSocket client will not attempt to reconnect and a new WebSocket client instance will need to be created in order to establish a new connection.

final socket = WebSocket(Uri.parse('ws://localhost:8080'));

// Later, close the connection with an optional code and reason.
socket.close(1000, 'CLOSE_NORMAL');

所屬分類

依賴

依賴清單 3 項

原始碼儲存庫

使用此套件的專案

所在榜單