e31fc1e57d
- Preventing from closing long polling transport with 204 in case of error - Reporting an error to the client if WebSocket was not closed normally Note in case of ServerSentEvents it is not possible on the client to tell the difference between when the server closed event stream due to an exception or because the client left OnConnectedAsync. In both cases the client sees only that the stream was closed. Part of: #163 |
||
|---|---|---|
| build | ||
| client-ts | ||
| samples | ||
| specs | ||
| src | ||
| test | ||
| typings | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| NuGet.config | ||
| NuGetPackageVerifier.json | ||
| README.md | ||
| SignalR.sln | ||
| appveyor.yml | ||
| build.cmd | ||
| build.ps1 | ||
| build.sh | ||
| version.props | ||
README.md
ASP.NET Core SignalR
AppVeyor:
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.
You can watch an introductory presentation here - Introducing ASP.NET Core Sockets.
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.
The JavaScript client is being published to our dev npm registry. The module contains a browserfied version of the client. You can install the module using the following command:
npm install signalr-client --registry https://dotnet.myget.org/f/aspnetcore-ci-dev/npm/