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

Fetcher: move to WS based fetcher #127

Closed
NuttyShrimp opened this issue Mar 29, 2024 · 0 comments · Fixed by #135
Closed

Fetcher: move to WS based fetcher #127

NuttyShrimp opened this issue Mar 29, 2024 · 0 comments · Fixed by #135
Assignees

Comments

@NuttyShrimp
Copy link
Member

As we have rewritten ronny in go, it has also moved to websocket for lower latency.
The current http fetcher should be replaced with a WS fetcher.
We should keep the HTTP fetcher and add the WS one, the right fetcher should be spawned based on the scheme in the URI (ws vs http)

@NuttyShrimp NuttyShrimp self-assigned this Mar 29, 2024
@NuttyShrimp NuttyShrimp moved this to In Progress in 12UL 23-24 Mar 29, 2024
@NuttyShrimp NuttyShrimp linked a pull request Apr 7, 2024 that will close this issue
@NuttyShrimp NuttyShrimp moved this from In Progress to Under Review in 12UL 23-24 Apr 15, 2024
@github-project-automation github-project-automation bot moved this from Under Review to Done in 12UL 23-24 Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant