TWS and IBGW 10.30 stable are perfectly fine to use. I run them with clients at API level 173 (that is something like 10.17.01) without any issues.
When you run IBKR provided TWS API implementations (such as the Java API I use), TWS API is very robust and provides backward and forward compatibility. Meaning that old clients work with newer TWS/IBGW and vice versa. During connection, the two negotiate the common TWS API level they use so that only messages known at that level are to be exchanged.
But IBKR provided TWS API implementations are even robust in case a client with an older TWS API gets exposed to a message from a newer version. That should not happen but, apparently does in some cases with TWS/IBGW 10.30 and some others. But that does not cause any issues, because:
- Message fields introduced by newer API versions are always added at the end of the message
- The bytes for all fields are accounted for in the message length header field
- EDecoder for older clients reads the entire message (even the bytes and fields it does not understand) and simply ignores any extra fields and bytes that it is not aware of.
Custom or non-IBKR TWS API implementations may not implement all these safeguards and would fail in these cases.
闯ü谤驳别苍
?
?
?
?
On Tue, Jan 21, 2025 at 08:17 PM, Lewis_Tang wrote:
So it seems 10.30 is not really a "stable" version. For those (including me) who are still on 10.19, should be directly update to 10.33 ?
