Exceptions thrown when sending or receiving messages would leave the WebSockets transport in a half-closed state when one of the loops is closed but the other one is still running preventing from the Connection.Closed event to be fired. Fixes: #412 |
||
|---|---|---|
| .. | ||
| Common | ||
| Microsoft.AspNetCore.SignalR.Client.FunctionalTests | ||
| Microsoft.AspNetCore.SignalR.Client.Tests | ||
| Microsoft.AspNetCore.SignalR.Common.Tests | ||
| Microsoft.AspNetCore.SignalR.Microbenchmarks | ||
| Microsoft.AspNetCore.SignalR.Tests | ||
| Microsoft.AspNetCore.Sockets.Common.Tests | ||
| Microsoft.AspNetCore.Sockets.Tests | ||
| Microsoft.AspNetCore.WebSockets.Internal.ConformanceTest | ||
| Microsoft.Extensions.WebSockets.Internal.Tests | ||
| WebSocketsTestApp | ||