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
{{ message }}
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.
Would it be ok to make the ConnectionId visible outside of HttpConnection?
Something like:
publicstringConnectionId=> _connectionId;
It could also be exposed through the Features property if you don't want to expose it directly like that.
Reason: When using the Sockets library, the client has no way of knowing its own ConnectionId.
I am working on a scenario where the client needs to send it to a notification service (think of it as a decentralized presence system).
The text was updated successfully, but these errors were encountered:
Would it be ok to make the
ConnectionId
visible outside ofHttpConnection
?Something like:
It could also be exposed through the
Features
property if you don't want to expose it directly like that.Reason: When using the Sockets library, the client has no way of knowing its own ConnectionId.
I am working on a scenario where the client needs to send it to a notification service (think of it as a decentralized presence system).
The text was updated successfully, but these errors were encountered: