this is connected to the frontend issue here
As a user, i will have my API interactions with web sockets go through a publish/subscribe structure
As a user, when i subscribe to a 'topic', i will be added to subscribers map, and my subscriber id will become associated with the appropriate topic ids as i subscribe to them. I should be able to interact with the topics that i want to subscribe or unsubscribe to, as well as remove myself from subscribers.
- our code should be able to create subscribers
- and be able to create topics
- as a subscriber, one should be able to subscribe to topics
- and unsubscribe to topics
- all subscribers should be able to list all topics they have subscribed to
- all topics should be able to list all of the subscribers subscribed to them
- we should be able to delete subscribers
- we should be able to delete topics
open questions:
is there a need for destroying subscriber objects on disconnect, or only on deletion (ie, user deletes account?) Mani believes we should keep everything in memory.
this is connected to the frontend issue here
As a user, i will have my API interactions with web sockets go through a publish/subscribe structure
As a user, when i subscribe to a 'topic', i will be added to subscribers map, and my subscriber id will become associated with the appropriate topic ids as i subscribe to them. I should be able to interact with the topics that i want to subscribe or unsubscribe to, as well as remove myself from subscribers.
open questions:
is there a need for destroying subscriber objects on disconnect, or only on deletion (ie, user deletes account?) Mani believes we should keep everything in memory.