aspnetcore/samples/ChatSample
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
..
Controllers
…
Data
…
Hubs Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
Models
…
Services
…
Views Fixing chat sample - it was still using fully qualified hub method name 2017-01-10 11:41:47 -08:00
wwwroot Introducing modules for the ts client 2016-11-29 12:35:33 -08:00
.bowerrc
…
ChatSample.xproj
…
Program.cs
…
Startup.cs
…
appsettings.json
…
bower.json
…
bundleconfig.json
…
compilerconfig.json
…
compilerconfig.json.defaults
…
project.json Fix EF.Tools version 2017-01-10 14:54:35 -08:00
web.config
…