Closed Despair2000 closed 5 years ago
yes, that’s is roughly correct BUT …
Currently under the hood IB4m aggregates all data associated with a particular historical data request (unique via id) while waiting for historicalDataEnd API call which signals the conclusion of the server response.
If use the new flag, historical data call will aggregate forever.
I see little need for this and just request real time bars.
Not that Interactive Brokers asked me, but I def have to question some of their recent API updates.
-abel
On Mar 21, 2019, at 11:17 AM, Despair2000 notifications@github.com wrote:
There is a fairly new function when issuing a historical data request. If you set the keepUpToDate flag one should receive realtime updates of the requested data.
This seems to be useful but I wonder if it is usable with IB4m? If I understand it right the updates should trigger a historicDataUpdate event and these don't exist in IB4m or am I wrong?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/softwarespartan/IB4m/issues/51, or mute the thread https://github.com/notifications/unsubscribe-auth/AEWq1LcLKVzw3e75uxPrOkkkaxmSKkQJks5vY6J5gaJpZM4cBrjS.
I'm with you on that. I already solved the situation with a separate realtime bar request like you also suggest. This seems to work fine. :-)
There is a fairly new function when issuing a historical data request. If you set the keepUpToDate flag one should receive realtime updates of the requested data.
This seems to be useful but I wonder if it is usable with IB4m? If I understand it right the updates should trigger a historicDataUpdate event and these don't exist in IB4m or am I wrong?