Enabling components to listen to any server-side change

[RubenVerborgh]

Need

• The Solid React components currently offer a way to listen to any changes (in addition to specific changes).
• Currently, this any is determined by subscribing to updates for every target URL of an outgoing HTTP request.
  • For example, if requests are made to http://a.com/12, http://b.com/45, then the React components will subscribe to the WebSockets running on both hosts, and trigger a refresh on any pub event.

Solution in solid-auth-client

• A request event is exposed, such that the React components see every request that is made with the fetcher.
  • Based on these URLs, a WebSocket is set up to every unique host.

Concerns with the existing solution

• solid-auth-client leaks all requests that any client-side library makes to all client-side librariess, which is a potential security issue.

Solution paths

• only expose hosts or WebSocket URLs (which are roughly equivalent; one comes from the other)
  • very solution-specific though
  • perhaps also a security problem
• remove the listen all functionality from the React components
  • then only listening to specific resources will be supported

[michielbdejong]

@NSeydoux Are you working on this? We need Websockets support for nodeSolidServer/node-solid-ws#1 (comment).

Would you accept a pull request?

[nicolasmondada]

This should be discussed in https://github.com/inrupt/solid-client-notifications-js.