16
Websocket: one connection, multiple payloads
Source: Kong/insomnia#5911 · opened by @lukepighetti
I have noticed that very few WebSocket server implementations expect someone to open one websocket connection for every type of message they want to send.
Instead, what is more popular, is opening a single WebSocket connection and then dispatching multiple different events to interact with a service.
This is currently hard to do in Insomnia.
What would be interesting to me, is having a folder-like WebSocket, which can contain multiple different payloads which can be run under it. The connection indicator would be on the top level WebSocket, not on the individual payloads
Instead, what is more popular, is opening a single WebSocket connection and then dispatching multiple different events to interact with a service.
This is currently hard to do in Insomnia.
What would be interesting to me, is having a folder-like WebSocket, which can contain multiple different payloads which can be run under it. The connection indicator would be on the top level WebSocket, not on the individual payloads
No pledges yet. Be the first to back this.
No comments yet.