socketcluster icon indicating copy to clipboard operation
socketcluster copied to clipboard

Highly scalable realtime pub/sub and RPC framework

Results 103 socketcluster issues
Sort by recently updated
recently updated
newest added

In a Dockerfile currently you need to supply a version tag and :latest is not supported making the examples fail to compose or to pull with ` docker pull socketcluster/socketcluster`...

Hello, I'd like to write (or find) some stress-testing or load-testing app where I can simulate many clients connecting to my socketcluster server. I saw this: https://github.com/SocketCluster/sc-stress-tests, but there is...

my state serevr is already running i run `set SCC_STATE_SERVER_HOST=127.0.0.1 && set SCC_BROKER_SERVER_PORT=3300 && node server.js` and i get the error ``` { SocketProtocolError: Socket hung up at SCClientSocket._onSCClose (D:\arash\socketCluster\scc-broker\node_modules\socketcluster-client\lib\scclientsocket.js:647:15)...

Sorry to be a pain... Ive been trying to do this on my own and am failing... First off, I'd like to use typescript. Its somewhat working. Second, and correct...

This should be the recommended approach instead of `worker.setAuthEngine(...)` and `worker.setCodecEngine(...)`.

Can you provide any references to clients who use it under high load in cluster environment in production to contact and ask them to share how SocketCluster works for them?...

@jondubois hey man is there an easy way to track this down? ``` 1|handler | 1527890188676 - Origin: Worker (PID 8416) 1|handler | [Error] SocketProtocolError: Socket hung up 1|handler |...

###env: 1: ingress rules: - host: sprd.nats.service http: paths: - path: /nats/scc-demo backend: serviceName: socketcluster servicePort: 8000 2: socketCluster.connect({host: 'sprd.nats.service:30001/nats/scc-demo', }) ###bug: Most of the time can be connected successfully...

Hi These days i involve in some project that need websocket (for phone application) and tcp (for iot device), and i made a "Net" tcp server and put it in...

Right now you can specify a global `ackTimeout` but it would be nice if this could also be specified as an option to `socket.emit(...)` - This should be implemented after...

enhancement