aspnetcore/samples/SocialWeather
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
..
Json add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
Pipe add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
Protobuf add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
wwwroot
FormatterResolver.cs add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
IStreamFormatter.cs add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
PersistentConnectionLifeTimeManager.cs Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
Program.cs add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
SocialWeather.xproj
SocialWeatherEndPoint.cs Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
Startup.cs add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
WeatherReport.cs add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
project.json add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
web.config