wboayue / rust-ibapi / 24273038064

85%

Build Type

push

github

Committed by web-flow

Commit Message

binary message ID framing for protobuf transport (#449)

* binary message ID framing for protobuf transport (phase 2)

- Add PROTOBUF_MSG_ID constant and encode_protobuf_message helper
- Add raw_bytes/is_protobuf fields to ResponseMessage
- Bump version range to v201..221 (PROTOBUF..UPDATE_CONFIG)
- Encode start_api as protobuf when server >= v201
- Detect protobuf vs text messages via binary message ID in read_message
- Add protobuf-aware routing with RoutingEnvelope extraction

* extract shared parse_raw_message, add protobuf path tests

- Extract duplicated read_message logic into parse_raw_message in common
- Add tests for protobuf, binary-id-text, and legacy text parse paths
- Add test for legacy format_start_api fallback
- Add TODO comments for protobuf error_code and routing tag assumptions
- Add comment clarifying mock version negotiation

* reduce duplication in encoding, routing, and message construction

- encode_length delegates to encode_raw_length
- extract is_order_message/is_shared_message helpers in routing
- add ResponseMessage::from_binary_text constructor

* move RoutingEnvelope to module scope

* fmt

* handle protobuf NextValidId, ManagedAccounts, Error during connection setup

Server at v201+ may send these startup messages as protobuf. Decode
proto payloads instead of reading text fields when is_protobuf is set.

* use binary message ID framing for all outgoing messages at v201+

Server at v201+ expects 4-byte BE binary message ID instead of text.
Without this, server cannot parse requests and never responds.

* consolidate notice logging in parse_account_info Error branch

Coverage Stats

91 of 138 new or added lines in 5 files covered. (65.94%)

2 existing lines in 2 files now uncovered.

8831 of 10335 relevant lines covered (85.45%)

124.61 hits per line