-
Notifications
You must be signed in to change notification settings - Fork 13
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
Interoperability with other implementations of FNV-1a #2
Comments
So, there are two issues at hand here:
|
I hadn't noticed this before, but it makes sense now: the reference |
@mjradwin I think I've resolved your issue. See: https://github.com/tjwebb/fnv-plus/blob/master/spec/fnv-plus.js#L110-L127 |
Awesome, thanks! I will pull the latest and confirm your fix. |
Great, let me know. |
Pulled 1.2.7 from npm and everything's working great! |
Excellent. Thanks for your feedback |
How would you propose using your
fnvplus.seed()
API to support using the standard offset_basis values as described in draft-eastlake-fnv-06.txt?We would like to be able to initialize fnvplus so it is compatible with Appendix C: A Few Test Vectors :
In our Java application, we generate unique IDs using 64-bit FNV-1a. For the same given string we would like to be able to generate the identical hash values in JavaScript using fnv-plus. The
fnvplus.seed()
implementation does allow the caller to specify a seed value, but that value is transformed (through hashing) so it can't be used as an offset_basis.The text was updated successfully, but these errors were encountered: