パッケージ、リポジトリ、アプリカテゴリを検索

パッケージ詳細v3.0.0

connecteo

connectivity_plus をラップし、追加のデータ接続チェックを追加するプラグインです。

30日間ダウンロード
1380
いいね数
69
Pub ポイント
80

パッケージをインストール

flutter pub add connecteo

パッケージ概要

公開情報に基づく選定ガイドです。参考としてご利用ください。

Connecteo は、connectivity_plus を拡張して、強化されたネットワーク接続状態のモニタリングを提供する Flutter プラグインです。データ接続の信頼性に関する追加チェックを提供し、デバイスがオンラインかどうかだけでなく、接続の品質や種類も検出できるようにします。堅牢なネットワーク認識を目的としており、リアルタイム更新をサポートし、信頼性の高い接続検出が必要なアプリにシームレスに統合できます。直感的な API を使ってネットワーク状態の変更を簡単に処理でき、安定したインターネットアクセスに依存するアプリに最適です。

用途

  • リアルタイムアプリ接続モニタリング
  • オフラインモードの検出
  • データ使用の最適化
  • ネットワーク品質の評価
  • 接続に基づくアプリ動作の適応
  • バックグラウンド同期管理

主な機能

  • 基本的なオンライン/オフラインを超える強化された接続チェック
  • モバイルおよびWi-Fiデータ接続タイプのサポート
  • リアルタイム接続状態の更新
  • 既存の connectivity_plus ワークフローとの簡単な統合
  • 軽量で最小限の依存関係
  • クロスプラットフォーム互換性

適している対象

  • 信頼できるネットワーク状態を必要とするアプリ
  • connectivity_plus を使用している開発者はすでに
  • オフライン機能を備えたアプリケーション
  • リアルタイム通信または同期機能
  • モバイルアプリはデータ使用に敏感です
  • ネットワークを意識したUI/UXデザイン

注意事項

  • 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 件

ソースリポジトリ

このパッケージを使用しているプロジェクト

データはまだありません。