Hello,
I have a problem with Event Time-s differing for the same points on multiple clients. We run multiple stream parallel, and deduplicate the results for redundancy, but the E aka Event Time field makes this difficult. Most of the time, this can be solved by just zeroing out the event time, but for markPrice data this does not work since it does not have a consistent timestamp for it. Wouldn’t it make sense for this data to have a Timestamp field as well that’s consistent across streams? Binance API Documentation
. We run multiple stream parallel, and deduplicate the results for redundancy
Why there’s need to run parallelly for the same streams?
Wouldn’t it make sense for this data to have a Timestamp field as well that’s consistent across streams?
Do you mean, in one WS connection, the @markPrice’s event should have a timestamp field whose value should be the same as in other streams under the same connection?
This wouldn’t make sense, the E field represents the time the JSON payload was created and it’s just expected that different streams have its events created at different times.