Crate architect_api

Source

Re-exports§

pub use auth::user_id::UserId;
pub use orderflow::OrderId;
pub use typed_message::MaybeSplit;
pub use typed_message::MessageTopic;
pub use utils::amount::Amount;
pub use utils::component_id::ComponentId;
pub use utils::dir::Dir;
pub use utils::dir_pair::DirPair;
pub use utils::duration::HumanDuration;
pub use utils::envelope::Address;
pub use utils::envelope::Envelope;
pub use utils::envelope::Sequence;
pub use utils::envelope::Stamp;
pub use utils::half_open_range::HalfOpenRange;
pub use utils::maybe_file::MaybeFile;
pub use utils::secrets::MaybeSecret;
pub use utils::str::Str;
pub use account::*;

Modules§

account
Accounts represent physical external accounts, mapped by the cpty (only partially user-defined, when the cpty can’t disambiguate). There isn’t a dichotomy between “internal” and “external” accounts– internal Architect subaccounting should be accomplished via Labels, and account re-labeling or grouping should be done via AccountGroups.
auth
cpty
external
External plugin wire protocol. Designed with cross-language, multi-encoding in mind.
folio
marketdata
misc
orderflow
Generic orderflow types used for oms/risk gateways, translateable to/from more specific cpty orderflow types
orderflow_v2
symbology
This is the protocol for sending symbology over the wire between the symbology server and clients, and from the loaders to the symbology server.
symbology_v2
This module contains the types we use to represent symbols and their metadata.
typed_message
utils

Macros§

expect_response
from_str_json
json_schema_is_string
match_response
pool
pool(vis, name, type, capacity, max_elt_size)
uuid_val
Implement a named wrapper type around a UUID