Expand description
BCS connectors and the BCS wire client.
Re-exports§
pub use brokapi_bcs_protocol as protocol;
Modules§
- cid
- The client order id codec: BCS accepts a full UUID as
clientOrderId. - config
- Configuration of the two connectors: the BCS client settings plus the choices of the connector itself (source label, reconnect pauses, buffer size).
- core
- The sans-io cores of the BCS connectors.
- error
- Maps the errors of the protocol layer ([
BcsApiError]) to the public [brokapi_core::Error]. - limits
- Loads
limits.toml(section[bcs]) throughBrokerLimits::from_toml_section. - map
- Mappers from the BCS wire models to the brokapi-core domain types.
- md
- The market data connector: order books, trades, quotes, candles and the instrument directory.
- pump
- WS event pumps: parse in the receiver task, never block on a slow consumer.
- raw
- Direct access to any BCS API method (the “back door”): same refresh token and access token, same
endpoint, same [
BrokerLimiter] as the connector it came from. - subs
- The subscription records a connector keeps, and the generator of subscription ids.
- ud
- The user data connector: orders, stop orders, portfolio and fills.
- util
- Small helpers shared by the two connectors: instrument ids, timeframes and timestamps.
Structs§
- BcsCid
Codec - BCS accepts full UUID strings as
clientOrderId(lossless, 128-bit). - BcsRaw
- A handle for calling any BCS API method with a connector’s token and rate limiter.
- Market
Data Config - Settings of
MarketDataConnector. - Market
Data Connector - BCS market data connector: order books, trades, quotes, candles and the instrument directory.
- MdCore
- Sans-io market data core of the BCS market data WebSocket.
- UdCore
- Sans-io user data core: order statuses, fills and portfolio updates from the WebSocket channels.
- User
Data Config - Settings of
UserDataConnector. - User
Data Connector - BCS user data connector: orders, stop orders, portfolio and the history of fills for one account.
Enums§
- UdFrame
- A frame for the user data core: a WebSocket push or a REST answer.
- UdRest
Frame - The answer of a REST call, given to the user data core by hand.