-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Expose client identity via a new abstract 'PeerUid' type #9952
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
Conversation
…g the actual remote uid private to prevent misuse.
|
|
| * one). If you want the uid to pass to some other Android API, consider one of the static wrapper | ||
| * methods of {@link PeerUids} instead (or propose a new one). | ||
| */ | ||
| public final class PeerUid { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@markb74, should this have @ExperimentalApi? Ditto for PeerUids
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems reasonable to me to start with this as experimental and stabilize in the future as needed. Doesn't seem like this would block our initial intended use case as there are other such classes being used without issue for now. I've added it, but let me know if we should revert for any reason.
…c#9952) The actual remote uid was kept private to prevent misuse.
While keeping the actual remote uid private to prevent misuse.