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
I saw it in the comment and so is in the code but I don't understand the reason behind the conversion?
"The reason for this is that the Lazy interface defaults to converting everything to hexadecimal whereas the Native interface assumes everything is non-hexadecimal"
Is there a benefit? Wouldn't the conversion add unnecessary overhead?
The text was updated successfully, but these errors were encountered:
The benefit of encoding is that you can store the encoded string safely in a database or anywhere. It is truly lazy. Unfortunately, yes, extra overhead would be added but I imagine this would be insignificant. Without encoding the byte array you are at risk of doing something risky to the byte array.
Plus, it is good to have a consistent encoding strategy throughout your project so Lazysodium stuck to hex encoding as its default. There was a MessageEncoder interface added to Lazysodium Android 4.1.1 so you can write your own encoder if you want https://github.com/terl/lazysodium-java/pull/70/files (Base64, Base32, etc)
I saw it in the comment and so is in the code but I don't understand the reason behind the conversion?
"The reason for this is that the Lazy interface defaults to converting everything to hexadecimal whereas the Native interface assumes everything is non-hexadecimal"
Is there a benefit? Wouldn't the conversion add unnecessary overhead?
The text was updated successfully, but these errors were encountered: