David Fowler 3b8e1a5380 Added a close timeout to the web socket transport ... - Today we don't end the request if the application completes but the websocket transport hasn't gotten the receive frame as yet. This changes adds a WebSocketOptions.CloseTimeout to EndPointOptions that allows configuring this timeout. When the timeout is reached, we abort the connection and end the transport task so that the request can end. - Added tests for websocket timeout and skipped tests for application timeouts		2017-04-04 09:59:41 -07:00
..
Common	Using common XUnitLoggerProvider	2017-03-27 16:19:40 -07:00
Microsoft.AspNetCore.SignalR.Client.FunctionalTests	Convert to netcoreapp2.0 (#338)	2017-03-25 09:37:39 -07:00
Microsoft.AspNetCore.SignalR.Client.Tests	Bugfix issue #355: Don't handle Invocation when no InvocationHandler … (#356)	2017-03-31 09:44:57 -07:00
Microsoft.AspNetCore.SignalR.Microbenchmarks	Convert to netcoreapp2.0 (#338)	2017-03-25 09:37:39 -07:00
Microsoft.AspNetCore.SignalR.Tests	React to CoreFx byte[] slice	2017-04-03 11:45:00 -07:00
Microsoft.AspNetCore.Sockets.Common.Tests	Convert to netcoreapp2.0 (#338)	2017-03-25 09:37:39 -07:00
Microsoft.AspNetCore.Sockets.Tests	Added a close timeout to the web socket transport	2017-04-04 09:59:41 -07:00
Microsoft.AspNetCore.WebSockets.Internal.ConformanceTest	Using common XUnitLoggerProvider	2017-03-27 16:19:40 -07:00
Microsoft.Extensions.WebSockets.Internal.Tests	React to CoreFx byte[] slice	2017-04-03 11:45:00 -07:00
WebSocketsTestApp	Convert to netcoreapp2.0 (#338)	2017-03-25 09:37:39 -07:00