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
Currently we use routing::MessageId to map responses to their respective responses. With the changes being brought in, can uuid be used instead?
routing::MessageId
The text was updated successfully, but these errors were encountered:
(aside) nanoid looks better to me than uuid. it's similarly a secure, URL-friendly, unique string ID scheme, which is simpler.
Sorry, something went wrong.
uuid is a well known standard and you can transfer it in binary form in 16 bytes or as an u128
No branches or pull requests
Currently we use
routing::MessageId
to map responses to their respective responses. With the changes being brought in, can uuid be used instead?The text was updated successfully, but these errors were encountered: