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

套件詳情v3.0.0

connecteo

包裝 connectivity_plus 並添加一些額外的資料連接檢查的外掛程式。

近 30 天下載
1380
喜歡數
69
Pub 分數
80

安裝套件

flutter pub add connecteo

套件介紹

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

Connecteo 是一個 Flutter 插件,透過擴展 connectivity_plus 提供增強的網路連線狀態監控。它提供額外的資料連線可靠性檢查,幫助開發者不僅檢測裝置是否線上,還能檢測連線品質與類型。此套件專為強大的網路感知設計,支援即時更新,並可無縫整合至需要可靠連線檢測的應用程式中。該套件透過直覺的 API 簡化網路狀態變化的處理,非常適合依賴穩定網際網路存取的應用程式。

適用情境

  • 即時應用連接監控
  • 離線模式檢測
  • 資料使用優化
  • 網路品質評估
  • 基於連接的App行為適應
  • 背景同步管理

主要特色

  • 增強的連接性檢查,超出基本的線上/離線狀態
  • 支援行動與Wi-Fi資料連接類型
  • 即時連接狀態更新
  • 與現有 connectivity_plus 工作流程的簡單整合
  • 輕量且依賴極少
  • 跨平台相容性

適合對象

  • 需要可靠網絡狀態的應用程式
  • 使用 connectivity_plus 的開發者已經
  • 具有離線功能的應用程式
  • 即時通訊或同步功能
  • 行動應用程式對資料使用敏感
  • 網路感知的使用者介面/使用者體驗設計

使用建議

  • Android 和 iOS 需要互聯網權限
  • 僅限連接狀態——無資料傳輸監控
  • 沒有內建的重試邏輯來處理連接失敗
  • 依賴於底層的 connectivity_plus 實現
  • 可能需要對弱訊號等邊緣情況額外處理

原始 README

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

connecteo

A plugin that wraps connectivity_plus and adds some checks that guarantee connection to the internet.

Contents

Motivation

connectivity_plus is a great package for checking internet status but comes with a single flaw - it checks only the connection type, not the internet connection data. It means that it can not guarantee you connection data, for example, when being under a Wifi access which does not have the internet connection. In such a scenario, the network requests will fail when theoretically they shouldn't due to being online.

A purpose of the plugin was to add some extra checks, on top on existing connectivity_plus's API, that make sure our connection to the internet is reliable when we are online.

Setup

You can install the package from your project's terminal:

flutter pub add connecteo

or add the dependency manually inside your pubspec.yaml:

dependencies:
  connecteo: # desired version

Then you can use connecteo's ConnectionChecker class wherever you want:

import 'package:connecteo/connecteo.dart';

final connecteo = ConnectionChecker();
// Sample checking the internet connection
final hasInternetConnection = await connecteo.isConnected;

How it works

The statement about a reliable internet connection is true when all these conditions are met:

  • A new (or previous) connection type is the online one - it is kind of self-explanatory. The connection type cannot be .none. Every other type is classified as online.
  • (On native platforms) A socket connection has to be opened and successfully established against at least one address - ConnectionChecker defines a default list of IP addresses that are globally available DNS resolvers. When at least one socket connection succeeds with its address, the information about the successful connection is returned, signaling the data connection. On the other hand, when all the socket connection trials fail, the ConnectionChecker informs about a lack of internet connection.
  • (on the Web platform) - situation here is similar to the native platform, but instead of the socket connection, the http call is being made. If we receive a response with 200 status code from one URL at least, the information about a successful connection is returned.
  • (optional) a response from the provided Base Url address has to be successful - if host address for the Base Url was provided in ConnectionChecker constructor, the host lookup is being made against the Base Url. If the lookup process will finish successfully without any SocketException then the condition is being met. This check was dictated by cases where an internet connection got back from an offline state, but the requests to the Base Url were failing for the first few seconds. It was causing some confusion because, in the majority of cases, we expect successful requests once the connection gets back online.

Usage

ConnectionChecker init

There are a couple of parameters (with its default values) that the ConnectionChecker's constructor takes - you can modify them to suit your needs:

  • checkHostReachability - let's you specify if you want to open the socket connections on native platforms (or make an http call on a web platform) against the list of addresses. Its default value is set to true.
  • checkConnectionEntriesNative - a list of custom ConnectionEntry which will be used to open the socket connections. The default list contains three ip addresses: CloudFlare (1.1.1.1), Google (8.8.4.4) and OpenDNS (208.67.222.222). This argument should be used only on native platforms.
  • checkConnectionEntriesWeb - a list of custom ConnectionEntry which will be used to check the responses from urls. At least one of the provided urls here has to return a response with an http status 200. The default list contains the following addresses: https://one.one.one.one/, https://jsonplaceholder.typicode.com/posts/1 and http://worldtimeapi.org/api/timezone. This argument should be used only on Web platforms.
  • hostReachabilityTimeout - let's you specify the Duration which is being used for the timeout for each ConnectionEntry and its socket's opening. The default value is 3 seconds.
  • baseUrlLookupAddress - a String URL which indicates the address you want to lookup during connection checks. Once you provide your URL, the connectionStream and isConnected will return true values only after a successful host lookup. Its default value is null.
  • requestInterval - it is a Duration which is being used for the interval how often the internet connection status should be refreshed. By default, its value is set to 3 seconds.
  • failureAttempts - the number of maximum trials between changing the online to offline state.When the lost connection won't go back after number of failureAttempts, the connectionStream and isConnected will return false values until the connection gets back. The default value is set to 4 attempts.

Example:

final connecteo = ConnectionChecker(
    checkHostReachability: true,
    checkConnectionEntriesNative: [
        ConnectionEntry.fromIpAddress(
            '1.0.0.1', // CloudFlare
        ),
        ConnectionEntry(
            '208.67.220.220', // OpenDNS
            ConnectionEntryType.ip,
        ),
    ],
    checkConnectionEntriesWeb: [
        ConnectionEntry.fromUrl(
            'https://one.one.one.one/', // CloudFlare
        ),
    ],
    hostReachabilityTimeout: Duration(seconds: 5),
    baseUrlLookupAddress: 'https://pub.dev/',
    failureAttempts: 7,
    requestInterval: Duration(seconds: 5),
);
get connectionStream

Returns the reliable internet connection status with the help of Stream<bool>. It yields its value every time when connection type will change or desired interval (ConnectionChecker's constructor argument) will pass.

Example:

final connecteo = ConnectionChecker();

final subscription = connecteo.connectionStream.listen((isConnected) {
    if (isConnected) {
        // Handle the logic when the app is online
    } else {
        // Handle the logic when the app is offline
    }
});
get isConnected

Returns the actual, reliable internet connection status for the present moment. Similar to above, but its return type is Future<bool>.

Example:

final connecteo = ConnectionChecker();

final hasInternetConnection = await connecteo.isConnected;
if (hasInternetConnection) {
    // Handle the one-time check when the app is online
}
get connectionTypes

Returns the current connection type.

Example:

final connecteo = ConnectionChecker();

final types = await connecteo.connectionTypes;
if (types.contains(ConnectionType.mobile)) {
    // Handle the logic when the application uses cellular data
}
untilConnects()

A method which resolves as soon as internet connection status get back from offline state. Handy when you want to trigger some kind of action once, after internet data connection get back but you do not want to use the connectionStream.

Example:

final connecteo = ConnectionChecker();

connecteo.untilConnects().then((_) {
    // Handle the logic when the internet connection data get back
});
Custom network checker

In the ConnectionChecker there's a factory method fromReachabilityChecker designed for integrating custom network checker implementations. To begin, you'll need to create a class that extends HostReachabilityChecker and implements 2 methods hostLookup and canReachAnyHost.

Note If you don't want to use one of those canReachAnyHost or hostLookup methods, simply return true`.

Let's look at parameters of fromReachabilityChecker constructor:

  • hostReachabilityChecker - it is a custom implementation of network checker.
  • requestInterval - it is a Duration which is being used for the interval how often the internet connection status should be refreshed. By default, its value is set to 3 seconds.
  • failureAttempts - the number of maximum trials between changing the online to offline state.When the lost connection won't go back after number of failureAttempts, the connectionStream and isConnected will return false values until the connection gets back. The default value is set to 4 attempts.

Example:


class CustomReachabilityChecker extends HostReachabilityChecker {
// TODO implementation 
}

final connecteo =  ConnectionChecker.fromReachabilityChecker(
  hostReachabilityChecker: CustomReachabilityChecker(),
  failureAttempts: 7,
  requestInterval: Duration(seconds: 5),
);

For more detailed information about the package possibilities, visit the API documentation.

所屬分類

依賴

依賴清單 3 項

原始碼儲存庫

使用此套件的專案

暫無相關資料。