Skip to content

Port socketserver to use channels and JSON based protocol#19782

Draft
64-bitman wants to merge 24 commits intovim:masterfrom
64-bitman:socketserver_channel
Draft

Port socketserver to use channels and JSON based protocol#19782
64-bitman wants to merge 24 commits intovim:masterfrom
64-bitman:socketserver_channel

Conversation

@64-bitman
Copy link
Copy Markdown
Contributor

@64-bitman 64-bitman commented Mar 21, 2026

This is not backwards compatible with the old protocol, but I think it is worth it. Using JSON is much simpler instead of trying to understand some arcane custom binary protocol.

@64-bitman 64-bitman force-pushed the socketserver_channel branch 5 times, most recently from d9aeb75 to b4fca02 Compare March 24, 2026 03:04
Comment thread src/socketserver.c Fixed
@64-bitman 64-bitman force-pushed the socketserver_channel branch 6 times, most recently from 602d848 to a203698 Compare March 25, 2026 02:10
@64-bitman
Copy link
Copy Markdown
Contributor Author

@pemensik Can you test if this PR fixes your issue? Thanks

@pemensik
Copy link
Copy Markdown

Note: JSON has a binary alternative in standardized CBOR protocol. It might be better suited for some binary blobs exchange. It can even represent JSON.

@64-bitman 64-bitman force-pushed the socketserver_channel branch from a4ee703 to 5e8e11c Compare March 25, 2026 15:59
@64-bitman
Copy link
Copy Markdown
Contributor Author

64-bitman commented Mar 25, 2026

Note: JSON has a binary alternative in standardized CBOR protocol. It might be better suited for some binary blobs exchange. It can even represent JSON.

Well there is no need to exchange binary blobs so JSON works fine

@64-bitman 64-bitman force-pushed the socketserver_channel branch 6 times, most recently from b620090 to e5ea406 Compare March 26, 2026 23:27
@64-bitman
Copy link
Copy Markdown
Contributor Author

@chrisbra Would this PR be accepted/OK? Thanks

@64-bitman 64-bitman force-pushed the socketserver_channel branch 3 times, most recently from 7e7c435 to 632bf6b Compare March 29, 2026 21:46
@64-bitman 64-bitman force-pushed the socketserver_channel branch from 6b76d92 to bbd2afd Compare April 6, 2026 14:07
@64-bitman
Copy link
Copy Markdown
Contributor Author

@chrisbra just checking if you didn't see the previous comment

@64-bitman 64-bitman force-pushed the socketserver_channel branch from bbd2afd to 0c00bfc Compare April 9, 2026 00:43
@64-bitman 64-bitman force-pushed the socketserver_channel branch from 0c00bfc to bef8bdf Compare April 9, 2026 01:06
@64-bitman 64-bitman force-pushed the socketserver_channel branch from bef8bdf to e01b83b Compare April 9, 2026 01:08
@chrisbra
Copy link
Copy Markdown
Member

chrisbra commented Apr 9, 2026

Yes I think this makes sense, even so this would be slightly backwards compatible. But I doubt this is a problem in practice as I have mentioned before

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants