tgpholly
/
tcp-ws-proxy
1
0
Fork 0
Code Issues 3 Pull Requests Packages Projects Releases 2 Wiki Activity

Use one websocket per client instance #2

New Issue
Open
opened 2024-01-19 10:33:05 +00:00 by tgpholly · 0 comments
tgpholly commented 2024-01-19 10:33:05 +00:00
Owner
Copy Link

Right now when the client gets a TCP connection it opens a new Websocket connection just for that connection. This is pretty bad. It would be better to have a pool of websocket connections (of configurable size) that the client can send it's local client's data down.

Right now when the client gets a TCP connection it opens a new Websocket connection just for that connection. This is pretty bad. It would be better to have a pool of websocket connections (of configurable size) that the client can send it's local client's data down.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
tcp
1.0.1
1.0.0
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tgpholly/tcp-ws-proxy#2
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?