Skip to content
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

feat(server): add SubscriptionSink::connection_id #1175

Merged
merged 1 commit into from
Aug 10, 2023

Conversation

niklasad1
Copy link
Member

Similar to #1163, added to provide uniform APIs

@niklasad1 niklasad1 requested a review from a team as a code owner August 9, 2023 15:56
@@ -322,6 +322,11 @@ impl SubscriptionSink {
self.method
}

/// Get the connection ID.
pub fn connection_id(&self) -> ConnectionId {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing!

Different topic: Would it also be possible to identify the client connected by this ConnectionID? (paritytech/substrate#14734)

Copy link
Member Author

@niklasad1 niklasad1 Aug 10, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that should work but the connection IDs may be reused once the connection is dropped and the counter wraps.

I guess that could handled when the subscription is dropped then just remove it from a HashMap or something

@niklasad1 niklasad1 merged commit 098766d into master Aug 10, 2023
@niklasad1 niklasad1 deleted the na-server-subscription-sink-add-connection-id branch August 10, 2023 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants