-
Notifications
You must be signed in to change notification settings - Fork 121
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
Feature Request : To have the Solid Notifications with Websockets work with multiple CSS workers. #1809
Comments
@argahsuknesib Can we generalize this to "notifications need to work with multiple threads", such that the existing multi-threaded Webhooks are valid solution? (WebSockets are not a well-scalable technique in general, hence Solid moving away from it.) |
Would Streaming HTTP help in any way? Or is the issue common for any channel type, where the client keeps an open connection to the server? There is also |
That is probably going to be the case indeed. The problem is if the thread that generates the change is different from the one having the open websocket/connection, that information would be lost as this is currently not communicated between threads. Webhooks doesn't have this problem though. |
I don't see how Webhook, LDN or any channel type using sendTo could be used by a browser application. They all rely on the sender to establish a connection with the receiver, for both Webhook and LDN it is an HTTP request. I think in the browser or more generally any notification receiver running on the user's device will use channel type based on reciveFrom. |
Actually the Web Push channel type could be a solution here. The current spec is outdated but we can prioritize drafting an updated version. Especially if there is an interest in implementing it. |
Environment
Description
Currently, the solid notifications with websockets do not work with multiple worker threads. Multiple worker threads are important to scale the CSS to be able to handle more than 50 GET requests/second especially in case with multiple solid pods per server.
The text was updated successfully, but these errors were encountered: