websocket-manager icon indicating copy to clipboard operation
websocket-manager copied to clipboard

Real-Time library for ASP .NET Core

Results 37 websocket-manager issues
Sort by recently updated
recently updated
newest added

First of all, thank you for all the great work and time you spent developing the WebSocketManager. I was wondering if you will consider publishing a new version of the...

This PR adds support for sending raw text messages that are not enclosed in the JSON serialized message envelope which is not always desirable.

I try to send message in websocket from other soft, wich must send only string. I intercept string in demo chat and have this: { "$type": "WebSocketManager.Common.Message", "messageType": 1, "data":...

Since the middleware is scoped differently in the service registration - it won't allow something to either be injected (obviously) or created inside that scope that is not scoped the...

I tried this but no success. InvocationDescriptor invocation = new InvocationDescriptor(); invocation.Identifier = Guid.Parse(_clientId); invocation.MethodName = "CallServer"; await _connection.SendAsync(invocation); on the server: public async Task CallServer() { }

from debug console: Sending through HTTP to a controller:test VM117:1 Uncaught SyntaxError: Unexpected token o in JSON at position 1 at JSON.parse () at WebSocket.socket.onmessage (WebSocketManager.js:106) socket.onmessage @ WebSocketManager.js:106

https://github.com/radu-matei/websocket-manager/blob/master/samples/ChatApplication/ChatHandler.cs#L11 In one sample, a dependency needed for the handler is newed-up rather than injected using dependency injection. This should not be handled by the user of the library, but...

May I know what is the json format to sent message? I want to sendmessage from desktop application. The example only has javascript library.

So when I try passing a complex type into or recieving one back from the library - I get json serialization errors... So basically, if I am wanting to send...

As I understand right now, SignalR will be supported for versions >= .NET Core 2.1 (and I assume .NET Standard 2.1), so I believe it is worth exploring and investigating...