huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
aspnetcore/test
History
David Fowler cd9ed9228a Remove streaming transport as a top level API (#110) 
- Remove Streaming* classes from Sockets. The main
API will be channels based and streaming transports
will use the PipelineChannel (formerly FramingChannel) to
access messages.
- Added WriteAsync and ReadAsync to Connection and hid
the IChannelConnection from public API.
- Also fixed the fact that unknown methods caused server side
exceptions.
- Changed the consumption pattern to WaitToReadAsync/TryRead to avoid
exceptions.
- React to API changes
 		2017-01-11 04:01:49 -08:00
..
Microsoft.AspNetCore.SignalR.Client.FunctionalTests Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
Microsoft.AspNetCore.SignalR.Test.Server Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
Microsoft.AspNetCore.SignalR.Tests Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
Microsoft.AspNetCore.Sockets.Client.Tests add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
Microsoft.AspNetCore.Sockets.Tests Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
Microsoft.AspNetCore.WebSockets.Internal.ConformanceTest add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
Microsoft.Extensions.WebSockets.Internal.Tests Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
WebSocketsTestApp add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00