Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Polling Transport #146

Closed
lachlan2k opened this issue Dec 6, 2023 · 2 comments
Closed

Polling Transport #146

lachlan2k opened this issue Dec 6, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request needs testing (on unstable) A feature that now exists, but is looking for people to test and use it

Comments

@lachlan2k
Copy link
Contributor

It would be great if RSSH could support polling over HTTP(S) as a transport, à la ferryman.

Very useful for when you only have HTTP/HTTPS as your egress, and websockets don't work.

@NHAS NHAS added the enhancement New feature or request label Dec 6, 2023
@NHAS NHAS self-assigned this Mar 27, 2024
@NHAS
Copy link
Owner

NHAS commented Apr 13, 2024

The first version of this now exists on unstable.

Its still quite broken, clients that disconnect arent removed from the connection list, its a bit inefficient, etc. But its there.

Im going to do some cleanup.

Todo:

  • Disconnect clients correctly
  • Limit connections to only public keys we know (using public keys are a password)
  • Limit max number of connections per public key
  • Customize comms path

@NHAS NHAS added the needs testing (on unstable) A feature that now exists, but is looking for people to test and use it label Apr 13, 2024
@NHAS
Copy link
Owner

NHAS commented Apr 13, 2024

This is now ready enough to be on unstable for testing

@NHAS NHAS closed this as completed Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs testing (on unstable) A feature that now exists, but is looking for people to test and use it
Projects
None yet
Development

No branches or pull requests

2 participants