Reliable Realtime Notification Preferences for Stock Trading Watchlist Testing
Short answer: model notification preferences as durable state, then test delivery as an at-least-once, reconnectable workflow; timing should affect when an event arrives, never whether the watchlist eventually converges. For a stock trading watchlist, “online” is not a cosmetic badge. A trader may mute price alerts, keep fills enabled, and open the same list on two devices. The useful contract is therefore precise: the server owns preference state and an ordered change identifier, while each client owns a cursor, a local view, and a replay request after a reconnect. I would decide those invari
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in