Liangying.Wei

Yes, it can. Sharing token means sharing the user info, which means all the connections for this client is one user. Could you share with us your scenario to share...

> If that's the case, no other clients may be able to connect to the signalr service, since signalr service allows X number of connections Yeah, that's the challenge when...

You can abort the connection in Hub when OnConnectedAsync if the connections from one client exceeds your expectation using `Context.Abort()`

@kwasak For Serverless there is no such feature exposed yet, we are adding the feature and they will be available soon. (REST API for closing a connection will be available...

Thanks for reporting the issue, a memory dump is very much appreciated. Thanks.

@CalinMPopa How about share it with OneDrive and emailing me `[email protected]` the link?

Back-pressure. When server-side is sending a lot of messages constantly to service-side, when message sending is slow/large/blocked, other messages are waiting for the write `semaphore` to release, and more WriteMessage...

Hi @sashafencyk is the workaround described here https://github.com/Azure/azure-signalr/issues/660#issuecomment-545793289 helpful? > set more server connections so that each server connection can have less burden delivering messages

@davidfowl, any thoughts?

Could we link to the spec doc or describe the design in the pr?