SolidLabResearch/decentralized-stream-notifications-aggregator

Issues

• Support WebSocketChannel2023 for the Solid Notifications Aggregator.

  #16 opened 6 months ago
  1

• Add support to monitor the LDES stream as well as the inbox incase new container is created and the inbox is updated.

  #15 opened 6 months ago
  0

• Implement usage of the same websocket channel if already subscribed to a resource.

  #14 opened 6 months ago
  0

• add support for a client to be able to subscribe to multiple ldes streams.

  #12 opened 6 months ago
  0

• What is the incentive for the client to use the notifications aggregator?

  #11 opened 5 months ago
  1

• Is there a point of the Redis Cache anymore?

  #10 opened 5 months ago
  1

• Implement a websocket based interface for the clients to interact with the server.

  #9 opened 6 months ago
  0

• add support to get the most recent cache from the server.

  #8 opened 6 months ago
  0

• Ensure 100% test coverage.

  #7 opened 6 months ago
  0

• Update the README of the repository.

  #6 opened 6 months ago
  0

• Benchmarking and optimizing the number of concurrent clients the cache server can handle.

  #5 opened 5 months ago
  5

• Utility functions to get the historical events from the cache between one timestamp to the other.

  #4 opened 6 months ago
  0

• Utility functions to get the latest notifications.

  #3 opened 6 months ago
  0

• Implement the notification stored logic.

  #2 opened 6 months ago
  0

• Implement support for notifications caching from multiple solid pods.

  #1 opened 6 months ago
  0