You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 18, 2023. It is now read-only.
As explained in this issue in the original PSync project, when PSync computes a murmurhash on an NDN name, it currently uses the name URI string. But there are multiple ways to display the URI string and it is not guaranteed to be unique. Instead, the TLV encoding should be used.
The original PSync code has been updated in commit named-data/PSync@32ccfc4 . Similar changes should be made to this library where it calls murmurHash3 on an NDN name. As mentioned in the commit, this is a breaking change. The code used by all PSync participants would need to be updated.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As explained in this issue in the original PSync project, when PSync computes a murmurhash on an NDN name, it currently uses the name URI string. But there are multiple ways to display the URI string and it is not guaranteed to be unique. Instead, the TLV encoding should be used.
The original PSync code has been updated in commit named-data/PSync@32ccfc4 . Similar changes should be made to this library where it calls murmurHash3 on an NDN name. As mentioned in the commit, this is a breaking change. The code used by all PSync participants would need to be updated.
The text was updated successfully, but these errors were encountered: