Go to file
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
samples Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
src Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
test Remove streaming transport as a top level API (#110) 2017-01-11 04:01:49 -08:00
tools
.gitattributes
.gitignore
.travis.yml
CONTRIBUTING.md
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json
README.md Add AppVeyor and Travis tags 2016-12-19 10:57:42 -08:00
SignalR.sln Remove hosting references 2016-12-14 16:17:15 -08:00
appveyor.yml add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
build.cmd
build.ps1
build.sh
global.json add "messaging" endpoints and transports 2017-01-09 16:01:08 -08:00
makefile.shade
package.json

README.md

ASP.NET Core SignalR

AppVeyor: AppVeyor

Travis: Travis

ASP.NET Core SignalR is a new library for ASP.NET Core developers that makes it incredibly simple to add real-time web functionality to your applications. What is "real-time web" functionality? It's the ability to have your server-side code push content to the connected clients as it happens, in real-time.

This project is part of ASP.NET Core. You can find samples, documentation and getting started instructions for ASP.NET Core at the Home repo.

Note To build the project locally at this time you will need the TypeScript Compiler on your path.