Crate ironfix_engine 

IronFix Engine

High-level FIX engine facade for the IronFix protocol implementation.

This is the composition root: the only crate permitted to combine the session layer, the store, the transport codec and the tag=value codec.

This crate provides:

• Initiator: the client-side engine. Initiator::connect dials the counterparty over TCP, runs the Logon handshake, and hands the socket to a background reactor that owns framing, heartbeats and TestRequests, CompID validation, sequence-gap detection, ResendRequest / SequenceReset / gap fill, PossDupFlag and OrigSendingTime, ResetSeqNumFlag, resend-from-store replay, and session-level Reject.
• Acceptor: the server-side engine. Acceptor::serve runs the acceptor half of the Logon handshake on an inbound connection and hands the socket to the same reactor.
• Connection: a cheap-clone handle returned by both engines — send, logout, await close, read sequence numbers.
• OutboundMessage: the body you hand to Connection::send; the engine stamps the header, MsgSeqNum and trailer.
• Application: the QuickFIX-shaped callback trait (on_create / on_logon / on_logout / to_admin / from_admin / to_app / from_app), plus NoOpApplication.
• EngineBuilder: fluent configuration that terminates in a ready-to-run Initiator or Acceptor.

Both engines share the same internal session reactor (reactor): once a Logon handshake completes, the inbound-frame contract — sequence validation, gap recovery, identity and clock checks, heartbeating, and the Logout handshake — is identical for the two roles.

Current limitations

• There is no TLS, and no dictionary validation: ironfix-dictionary’s Validator is never invoked on the session path.
• The store is opt-in and in-memory. Attaching an ironfix_store::MemoryStore with Initiator::with_store enables resend-from-store replay, but there is no persistent implementation yet; the acceptor attaches no store, so its resends are gap-filled.

Re-exports

pub use acceptor::Acceptor;

pub use application::Application;

pub use application::NoOpApplication;

pub use application::RejectReason;

pub use application::SessionId;

pub use builder::EngineBuilder;

pub use connection::Connection;

pub use error::EngineError;

pub use initiator::Initiator;

pub use outbound::OutboundField;

pub use outbound::OutboundMessage;

Modules

acceptor

Server-side (acceptor) FIX engine: inbound connections, framing, and the acceptor half of the Logon handshake.

application

Application callback interface.

builder

Engine builder for fluent configuration.

connection

Live-session connection handle.

error

Engine error types.

initiator

Client-side (initiator) FIX engine: TCP dial, framing, and a live session reactor.

outbound

Outbound message builder and the rules an outbound body must satisfy.

Structs

SessionConfig

Configuration for a FIX session.