Keep synced with Binance Server Time or allow a time offset to be set about go-binance

[0cv]

@adshao thoughts ?

[adshao]

@Krisa Sorry for the late reply. Yes, I agree with you, an optional parameter useServerTime in https://github.com/jaggedsoft/node-binance-api#troubleshooting is more acceptable and useful in some cases than directly calling ntp synchronization in #125.

[adshao]

To support this feature, we could set useServerTime in https://github.com/adshao/go-binance/blob/master/client.go#L191 as a per request option.

[0cv]

@adshao The problem of useServerTime in the node binance library is that it does a one time request when the client is initialized and... that's it. If the app is running multiple days, we can easily get out of sync again. That's the opposite of #125, and not really better either.

I'd be more in favour of exposing the timeOffset here https://github.com/jaggedsoft/node-binance-api/blob/d011f5845a91c06a0f4ef32ff08bed31d53cb29e/node-binance-api.js#L1207 (or rather TimeOffset) in the Client https://github.com/adshao/go-binance/blob/master/client.go#L172 which can be overwritten. A function BinanceClient.NewSetTimeOffsetService().Do(context.Background()) could also accessory set this TimeOffset, but that would be nothing more than querying Binance time and putting it into TimeOffset. Actually node-binance is also having such function here https://github.com/jaggedsoft/node-binance-api/blob/d011f5845a91c06a0f4ef32ff08bed31d53cb29e/node-binance-api.js#L1979 (additionally to the init param)