05d6bbb782
There was a race condition between the first poll and any other http request that was sent. In particular, if you called StartAsync then StopAsync it was possible for the delete to happen before the poll started leading to 400 errors. This change fixes that by making the very first poll return immediately so that the client can use that to determine if there was an error connecting. |
||
|---|---|---|
| .. | ||
| spec | ||
| src | ||
| README.md | ||
| package-lock.json | ||
| package.json | ||
| rollup.config.js | ||
| tsconfig.json | ||
README.md
MsgPack support for SignalR for ASP.NET Core
Installation
npm install @aspnet/signalr-protocol-msgpack
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.
Example (Browser)
let connection = new signalR.HubConnection('/chat', {
protocol: new signalR.protocols.msgpack.MessagePackHubProtocol()
});
connection.on('send', data => {
console.log(data);
});
connection.start()
.then(() => connection.invoke('send', 'Hello'));
Example (NodeJS)
const signalR = require("@aspnet/signalr");
const signalRMsgPack = require("@aspnet/signalr-protocol-msgpack");
let connection = new signalR.HubConnection('/chat', {
protocol: new signalRMsgPack.MessagePackHubProtocol()
});
connection.on('send', data => {
console.log(data);
});
connection.start()
.then(() => connection.invoke('send', 'Hello'));