We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Generate a Hash key for each device when the library is starting up .
The Hash key will be generated once during the life cycle of the app, if does not exist
After authentication and authorization on both devices the sender will send their Hash key to the receiver.
The receiver will maintain a record of sending devices and their hash key in a SQLite table p2p_hash_keys.
p2p_hash_keys
If a sender sends a different Hash key than the previous known hashkey, the records in p2p_received_history for that device are deleted.
p2p_received_history
This means that all data in the sender should be sent to the receiver.
The text was updated successfully, but these errors were encountered:
ekigamba
Successfully merging a pull request may close this issue.
Generate a Hash key for each device when the library is starting up .
The Hash key will be generated once during the life cycle of the app, if does not exist
After authentication and authorization on both devices the sender will send their Hash key to the receiver.
The receiver will maintain a record of sending devices and their hash key in a SQLite table
p2p_hash_keys
.If a sender sends a different Hash key than the previous known hashkey, the records in
p2p_received_history
for that device are deleted.This means that all data in the sender should be sent to the receiver.
The text was updated successfully, but these errors were encountered: