-
Real-time subscription management in Dashboards
Dashboards opens a new subscription for every unique parameter [x] input to a streaming data service. This subscription remains active for the period of dashboard session, and is shared when multiple users make the same subscription request, e.g. multiple users requesting a real-time chart of EUR/USD will all feed off the one EUR/USD active subscription, offering performance optimization for typical sym driven subscription feeds.
Where things get more difficult is when multiple inputs are sent to .u.sub[], particulary if datetime is one of the input variables. Each datetime request is likely to be unique, so will open a new subscription; single users may have multiple subscriptions active at once. Complicating the issue is if a dashboard tab remains active in a browser, those subscriptions also remain active until the tab is closed (which may be never).
How best can these subscriptions be managed?
* Nice-to-have is an option to ‘kill’ the last subscription request made by the user, so a user can only have one active subscription at a time per data source (so if multiple subscriptions were needed, each would require its own data source).
* A timeout feature, to ‘kill’ the subscription if a user does not send a .u.sub[] request after a defined time (e.g. 12 hours); this is to help manage inactive tab sessions.
Are there any interim measures we could take?
-
This discussion was modified 1 week, 2 days ago by
dfallon.
-
This discussion was modified 1 week, 2 days ago by
-
0 Replies
Sorry, there were no replies found.
Log in to reply.