-
Notifications
You must be signed in to change notification settings - Fork 5
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
Run fula under a android forgrand service #52
Comments
@farhoud perfect, a PR for this would be great |
#54 |
Thank you Farhood. I am the one working on it |
So there are 2 services fula and wnfs. |
Let me share my reason for these question's. And another ting do you need android native notification? |
They are not scheduled jobs. WNFS is responsible for encryption and creating merkle dag from a file, amd fula transfers the created dag to blox. Also whenever user download a file, wnfs requests the needed cids and fula bring them to wnfs from blox and wnfs decrypt . So to the question: 1- i think if we keep libp2p connection always open, it drains battery and we need to turn it on when application is in foreground (open) and when app is in background or closed, schedule it to turn on and check for updates and then close the connection Did this answer all questions? |
My situation in Hoodchat was pretty much different and I need libp2p to always run. but based on this Documentation I think we can implement upload and download as Jobs and let the android job scheduler handle them:
but bounded service and foreground service are still an option. |
Doesn't always running libp2p connection means keeping it open and drains battery? |
Sure big time especially if I enable DHT and hole punching but that's the price of privacy. |
on android wrap the FULA client inside service
is the better way to run FULA clients this way:
If you need I can make PR. I have done it on a project like this with a more complicated interface.
The text was updated successfully, but these errors were encountered: