Removing sending OPTIONS request if WebSocket transport requested This removes session stickiness requirement for WebSockets Fixes: #1035 |
||
|---|---|---|
| .. | ||
| Microsoft.AspNetCore.SignalR.Client.TS | ||
| Microsoft.AspNetCore.SignalR.Client.TS.Tests | ||
| Microsoft.AspNetCore.SignalR.Test.Server | ||
| typings | ||
| .npmignore | ||
| README.md | ||
| package-lock.json | ||
| package.json | ||
README.md
JavaScript and TypeScript clients for SignalR for ASP.NET Core
Installation
npm install @aspnet/signalr-client
Usage
Browser
To use the client in a browser, copy *.js files from the dist/browser folder to your script folder include on your page using the <script> tag.
Node.js
The following polyfills are required to use the client in Node.js applications:
XmlHttpRequest- alwaysWebSockets- to use the WebSockets transportEventSource- to use the ServerSentEvents transportbtoa/atob- to use binary protocols (e.g. MessagePack) over text transports (ServerSentEvents)
Example
let connection = new signalR.HubConnection('/chat');
connection.on('send', data => {
console.log(data);
});
connection.start()
.then(() => connection.invoke('send', 'Hello'));