aspnetcore/test/Microsoft.Extensions.WebSoc...
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
..
Properties
Microsoft.Extensions.WebSockets.Internal.Tests.xproj
TestUtil.cs
Utf8ValidatorTests.cs
WebSocketConnectionExtensions.cs
WebSocketConnectionSummary.cs
WebSocketConnectionTests.ConnectionLifecycle.cs
WebSocketConnectionTests.PingPong.cs
WebSocketConnectionTests.ProtocolErrors.cs
WebSocketConnectionTests.ReceiveAsync.cs
WebSocketConnectionTests.SendAsync.cs Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
WebSocketConnectionTests.Utf8Validation.cs
WebSocketPair.cs Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
project.json add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00