cretezy / dsock

Distributed WebSocket broker

🚀 Website / Blog | YouTube | LinkedIn

---

Most recent blog posts:

• Self-hosted analytics: How to track 53% more views
• Become a git stash pro
• React Query + Axios for authentication
• My perfect Node server for Web APIs
• Flutter JSON vs Protocol Buffer: Benefits and performance
• Flutter JSON parsing: What is the fastest?

---

Most recent videos:

• Move Ten Times Faster in Neovim with Leap
• 5 Neovim Plugins To Improve Your Productivity
• What is Home Assistant? The Ultimate Smart Home Guide
• Svelte For React Developers
• Neovim With AstroNvim | Your New Advanced Development Editor

dsock's Issues

chat example using flutter and superstate ?

Seems like a logical architecture marriage ?

Additional transports

This is a question regarding this websocket broker implementation.

I case of a websocket connection does not succeeds does it fallback to another type of transport? i.e. XHR-streaming, Long-Polling, etc?

If not, are there any plans to implement something like this soon?

TCP Source

Hi there! I'm working on a project that involves a bidirectional TCP to websocket connection (e.g. a remote terminal using xterm.js and addon xterm-addon-attach). I'm trying to upgrade it to allow for multiple websocket clients.

The multi-client functionality of dSock looks very promising for that purpose! From what I can tell, incoming messages come via a POST endpoint, and I'm trying to figure out if there's a way to set it up with TCP.

I see that you have a project item for bidirectional data, as well as one for TCP connections instead of websockets. Would either of these allow me to set up bidirectional TCP to websocket connections? Do you have any plans to support a TCP connection on the server?

What format are the releases?

Hello

I downloaded from the releases and they have no extension .zip .exe. Is it an application release or archive?