You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to squeeze more rps out of questrade we need more keys and those keys have to be managed by a (set of) actor(s) that implement our streaming data feeds.
QTs free snap quotes allow use to implement real-time, low frequency data feeds up to the per account rate limits. If we want to allow multiple account holders to aggregate their keys for the benefit of a group of accounts (eg. higher qps (quotes per sec) for less symbols) we need to build out a manager service to handle a few things:
keys shared by participants not wanting to run their own data daemon should be usable even if they only allow the read_acc Oauth scope (see scopes at the bottom here)
there should be a graceful way to submit new keys / refresh expired keys with the manager daemon
a more sophisticated brokers.ini is required to describe the key set (and per key capabilities - i.e. oauth scopes) as well as what each key's use target is (eg. stocks vs. option quotes)
In order to squeeze more rps out of questrade we need more keys and those keys have to be managed by a (set of) actor(s) that implement our streaming data feeds.
QTs free snap quotes allow use to implement real-time, low frequency data feeds up to the per account rate limits. If we want to allow multiple account holders to aggregate their keys for the benefit of a group of accounts (eg. higher qps (quotes per sec) for less symbols) we need to build out a manager service to handle a few things:
read_acc
Oauth scope (see scopes at the bottom here)brokers.ini
is required to describe the key set (and per key capabilities - i.e. oauth scopes) as well as what each key's use target is (eg. stocks vs. option quotes)json
instead of the current arithmetic approach used currently.
The text was updated successfully, but these errors were encountered: