Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gomobile-lib] adapt network configuration according to the connectivity #10

Open
aeddi opened this issue Sep 19, 2019 · 1 comment
Open

Comments

@aeddi
Copy link
Member

aeddi commented Sep 19, 2019

In the Berty app, we have developed a system to update the network configuration according to the device's connectivity, it is currently complicated to extract this part from our code to integrate it to gomobile-ipfs but we will deal with it as soon as possible.

Android and iOS offer APIs that allow the OS to notify your application when a connectivity change occurs: 4G, Wifi, Bluetooth, internet access, etc....

Depending on the new state, several things are conceivable to save resources (CPU, network, etc...). For example:

  • modify the different watermarks
  • disable the mDNS if we are not connected to a LAN
  • disable the reconnection attempt to bootstrap nodes (see bootstrapConfig) if there is no internet access, set the Period to 5 seconds if we are connected via a cellular connection and to 30 if we are connected via wifi
  • etc....
@aeddi aeddi changed the title [gomobile-ipfs] adapt network configuration according to the connectivity [gomobile-lib] adapt network configuration according to the connectivity Sep 19, 2019
@jefft0 jefft0 added verified Bug is verified and removed verified Bug is verified labels Apr 24, 2023
@jefft0
Copy link
Collaborator

jefft0 commented May 4, 2023

The latest Berty does some of this. Should copy code from Berty. Putting on the backlog until we have resources to revisit.

@jefft0 jefft0 added the backlog label Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants