Skip to main content

Module application

Module application 

Source
Expand description

The application callback interface — the async equivalent of the seven classic QuickFIX callbacks.

Structs§

ChannelApplication
The Application half of event_channel: it forwards the notification callbacks onto the channel and accepts everything else with the trait defaults. Construct it only via event_channel.
DoNotSend
Returned by to_app to veto an outgoing (or resent) message.

Enums§

ApplicationError
Returned by from_admin / from_app to influence session behavior.
SessionEvent
A protocol event surfaced by event_channel. Every variant carries the SessionId it happened on, so one receiver can serve many sessions — match on the id to demultiplex.

Traits§

Application
Implemented by users of the engine. All callbacks run on the session’s task: a slow callback delays that session (only), exactly like the single-threaded session model of the reference engines.

Functions§

event_channel
Bridge the callback interface to a tokio channel: returns an Application to hand to crate::Engine::start, plus a receiver you drain from your own task or select! loop. This is the tokio-native alternative to implementing Application by hand — inbound events and your outbound crate::SessionHandle sends live in one place, with no callback reentrancy hazard.