Pakete, Repositories und App-Kategorien suchen

Paketdetailsv0.3.0

dio_http_cache

HTTP-Cache-Bibliothek für Flutter Dio, ähnlich wie RxCache. Verwendet sqflite als Festplatten-Cache und die LRU-Strategie von google/quiver-dart als Speicher-Cache.

AndroidiOSmacOS
30-Tage-Downloads
1550
Likes
248
Pub-Punkte
120

Paket installieren

flutter pub add dio_http_cache

Paketübersicht

Aus öffentlichen Paketdaten erstellte Orientierung.

Dio HTTP Cache ist eine Caching-Bibliothek für den HTTP-Client Dio in Flutter, die sowohl Speicher- als auch Datenträger-Caching bietet. Sie verwendet sqflite für die dauerhafte Speicherung auf dem Datenträger und implementiert eine LRU-Strategie (Least Recently Used) über google/quiver-dart zur effizienten Speicherverwaltung. Dieses Paket hilft, redundanten Netzwerk-Anfragen zu reduzieren, die App-Leistung zu verbessern und Bandbreite zu sparen, indem HTTP-Antworten zwischengespeichert werden. Ideal für Apps, die Offline-Unterstützung benötigen oder häufige API-Aufrufe mit stabilen Daten durchführen.

Anwendungsfälle

  • API-Antworten zwischenspeichern, um den Netzwerkverbrauch zu reduzieren
  • Aktivieren des Offline-Zugriffs auf zuvor abgerufene Daten
  • Verbesserung der App-Leistung durch verringerte Latenz
  • Effizientes Speichern von häufig zugegriffenen Daten
  • Verringerung der Serverlast durch zwischengespeicherte Antworten

Hauptmerkmale

  • Disk-Caching mit sqflite
  • LRU-Speicher-Cache mit quiver-dart
  • Automatischer Anfrage/Antwort-Cache
  • Konfigurierbare Cache-Ablaufzeit
  • Unterstützt GET- und HEAD-Anfragen

Geeignet für

  • Apps mit häufigen API-Aufrufen
  • Offline-fähige Anwendungen
  • leistungsoptimierte Netzwerkschichten
  • datenintensive Mobile-Apps
  • Entwickler, die Dio für HTTP-Anfragen verwenden

Hinweise

  • Benötigt sqflite-Einrichtung und Berechtigungen
  • Die Cache-Größe muss manuell verwaltet werden
  • Nicht geeignet für große Binärdaten
  • Beschränkt auf GET/HEAD-Methoden
  • Kann benutzerdefinierte Cache-Schlüssellogik für komplexe Anfragen erfordern

Original-README

Originaler README-Schnappschuss aus dem verknüpften Quell-Repository. Aktuelle Inhalte finden Sie im Repository.

dio-http-cache

Pub

中文介绍

Dio-http-cache is a cache library for Dio ( http client for flutter ), like Rxcache in Android.

Dio-http-cache uses sqflite as disk cache, and LRU strategy as memory cache.

Inspired by flutter_cache_manager.

Add Dependency
dependencies:
  dio_http_cache: ^0.3.x #latest version
QuickStart
  1. Add a dio-http-cache interceptor in Dio :

    dio.interceptors.add(DioCacheManager(CacheConfig(baseUrl: "http://www.google.com")).interceptor);
    
  2. Set maxAge for a request :

    Dio().get(
      "http://www.google.com",
      options: buildCacheOptions(Duration(days: 7)),
    );
    
The advanced
  1. Custom your config by buildCacheOptions :

    1. primaryKey: By default, host + path is used as the primaryKey, and you can also customize it.

    2. subKey: By default, query ( data or queryParameters) is used as subKey, and you can specify the subKey when it's necessary, for example:

      buildCacheOptions(Duration(days: 7), subKey: "page=1")
      
    3. maxAge: set the cache time. If the value is null or not setted, it will try to get maxAge and maxStale from response headers.

    4. maxStale: set stale time. When an error (like 500,404) occurs before maxStale, try to return cache.

      buildCacheOptions(Duration(days: 7), maxStale: Duration(days: 10))
      
    5. forceRefresh: false default.

      buildCacheOptions(Duration(days: 7), forceRefresh: true)
      
      1. Get data from network first.
      2. If getting data from network succeeds, store or refresh cache.
      3. If getting data from network fails or no network avaliable, try get data from cache instead of an error.
  2. Use "CacheConfig" to config default params

    1. baseUrl: it’s optional; If you don't have set baseUrl in CacheConfig, when you call deleteCache, you need provide full path like "https://www.google.com/search?q=hello", but not just "search?q=hello".
    2. encrypt / decrypt: these two must be used together to encrypt the disk cache data, you can also zip data here.
    3. defaultMaxAge: use Duration(day:7) as default.
    4. defaultaMaxStale: similar with DefaultMaxAge.
    5. databasePath: database path.
    6. databaseName: database name.
    7. skipMemoryCache: false defalut.
    8. skipDiskCache: false default.
    9. maxMemoryCacheCount: 100 defalut.
    10. defaultRequestMethod: use "POST" as default, it will be used in delete caches.
    11. diskStore: custom disk storage.
  3. How to clear expired cache

    • Just ignore it, that is automatic.

    • But if you insist : DioCacheManager.clearExpired();

  4. How to delete caches

    1. No matter what subKey is, delete local cache if primary matched.

      // Automatically parses primarykey from path
      _dioCacheManager.deleteByPrimaryKey(path, requestMethod: "POST"); 
      
    2. Delete local cache when both primaryKey and subKey matched.

      // delete local cache when both primaryKey and subKey matched.
      _dioCacheManager.deleteByPrimaryKeyAndSubKey(path, requestMethod: "GET"); 
      

      INPORTANT: If you have additional parameters when requesting the http interface, you must take them with it, for example:

      _dio.get(_url, queryParameters: {'k': keyword}, 
      	options: buildCacheOptions(Duration(hours: 1)))
      //delete the cache:
      _dioCacheManager.deleteByPrimaryKeyAndSubKey(_url, requestMethod: "GET", queryParameters:{'k': keyword}); 
      
      _dio.post(_url, data: {'k': keyword}, 
      	options: buildCacheOptions(Duration(hours: 1)))
      //delete the cache:
      _dioCacheManager.deleteByPrimaryKeyAndSubKey(_url, requestMethod: "POST", data:{'k': keyword}); 
      
    3. Delete local cache by primaryKey and optional subKey if you know your primarykey and subkey exactly.

      // delete local cache by primaryKey and optional subKey
      _dioCacheManager.delete(primaryKey,{subKey,requestMethod});
      
  5. How to clear All caches (expired or not)

    _dioCacheManager.clearAll();
    
  6. How to know if the data come from Cache

    if (null != response.headers.value(DIO_CACHE_HEADER_KEY_DATA_SOURCE)) {
     	// data come from cache
    } else {
     	// data come from net
    }
    
Example for maxAge and maxStale
_dio.post(
	"https://www.exmaple.com",
	data: {'k': "keyword"},
	options:buildCacheOptions(
  		Duration(days: 3), 
  		maxStale: Duration(days: 7), 
	)
)
  1. 0 ~ 3 days : Return data from cache directly (irrelevant with network).
  2. 3 ~ 7 days:
    1. Get data from network first.
    2. If getting data from network succeeds, refresh cache.
    3. If getting data from network fails or no network avaliable, try get data from cache instead of an error.
  3. 7 ~ ∞ days: It won't use cache anymore, and the cache will be deleted at the right time.
License
Copyright 2019 Hurshi

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

 http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Kategorien

Abhängigkeiten

Abhängigkeiten 7 Einträge

Quell-Repository

Projekte, die dieses Paket verwenden