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.
the current implementation of DefaultHubLifetimeManager.InvokeGroupAsync scans each connections metadata in the in the hope of find a connection with a matching group; this would result in wasteful resources when a name of a group that is not used/or has no connection is supplied, IMHO the default implementation should have an index of group names with a count of active connections to prevent this especially when a hub could have many connections.
The text was updated successfully, but these errors were encountered:
the current implementation of DefaultHubLifetimeManager.InvokeGroupAsync scans each connections metadata in the in the hope of find a connection with a matching group; this would result in wasteful resources when a name of a group that is not used/or has no connection is supplied, IMHO the default implementation should have an index of group names with a count of active connections to prevent this especially when a hub could have many connections.
The text was updated successfully, but these errors were encountered: