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

A suggestion regarding WebSocket consumers (searchers) #17

Open
iowar opened this issue May 24, 2023 · 1 comment
Open

A suggestion regarding WebSocket consumers (searchers) #17

iowar opened this issue May 24, 2023 · 1 comment

Comments

@iowar
Copy link
Collaborator

iowar commented May 24, 2023

it can be a better approach, although not urgent at the moment, to develop a general WebSocket package that provides a more flexible data flow for searchers. This package could include subscribing and unsubscribing mechanisms to the WebSocket channels once authentication is performed
Because searchers have been removed from P2P, it implies that there will be a need for new WebSocket channels when different types of data transfer are required

@ckartik
Copy link
Contributor

ckartik commented May 26, 2023

It will also be interesting to think about how we we will manage connecting searchers, if we want users running multiple boosts with each builder.
cc: @floodcode @kant777

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants