Group: Lolaf Staffix

Sort by:Popular▼

✓Popular✓Newest

The interfaces an application writes against - FixInitiator, FixAcceptor, FixSession and FixApplication, the settings that configure them, and the codec, store, logger, plugin and admin SPIs the other modules implement. Compile ...

The contracts every Spring Boot module implements so the starter can assemble an engine from properties: settings contributors for stores, loggers, plugins and admin APIs, and the post-processor that amends each session's settings ...

The encoding and decoding engine: the base classes every generated encoder extends, the field setters that bind a value to a tag, the decoders that present a wire message as a DecodedFixMessage, and the serdes that read and write each ...

Shared logger abstractions: the batching base class every logger extends, and the obfuscators that keep usernames and passwords out of a log of raw FIX.

The contract every message store must satisfy, shipped as a test-jar. Each store subclasses these abstract tests, so a behavioural difference between stores fails the build rather than hiding in one store's own tests.

Lolaf Staffix Admin

Primitive-keyed maps and indexable lists for the message path: Int2ObjectHashMap, Long2ObjectHashMap, IndexableList and IndexableMap. A lookup keyed by a tag or a sequence number neither boxes the key nor allocates, which the JDK's ...

The contract for the gRPC senders, shipped as a test-jar. Separate from staffix-http-client-test-kit because its stub server must send HTTP/2 trailers, which only the OkHttp and Jetty clients can read.

HttpSender on java.net.http. The default because it adds no dependency, not because it is the fastest: prefer staffix-http-client-okhttp for an HTTPS collector, or staffix-http-client-jetty over plaintext.

The contract every HttpSender must satisfy, shipped as a test-jar with a stub server to run it against. Each client module subclasses it, so a difference in behaviour between clients fails the build rather than hiding in one client's ...

The session state machine and the runtime behind the staffix-api interfaces: logon and logout, heartbeats and test requests, sequence numbers, resend requests and gap fills, the message parser, and the initiator and acceptor built on ...

Writes each message through SLF4J, so it lands wherever the application's logging is already pointed.

Keeps messages and sequence numbers in memory only: the fastest store, and the one that loses everything on restart. For tests, and for sessions that reset sequence numbers at every logon.

A session's settings as a document, read and written as YAML or JSON, with the JSON schema that the build generates from it and ships inside this jar, each field described by the settings' own documentation.

Holds session settings built in code, for an application that configures its sessions programmatically or in tests.

Builds a FixApplication from a class name, one instance per session, through its no-argument constructor. The factory for an application that nothing else is wiring.

Encoders and registries for the FIXT.1.1 session layer - logon, logout, heartbeat, test request and resend - which every FIX 5.0 version relies on for the session it runs over.

HttpSender on OkHttp 5, and the one to use for an HTTPS collector if the dependency is acceptable. One of the two clients that can also serve gRPC.

What both asynchronous wrappers are built on: a persistent queue backed by Chronicle Queue, the events and serdes that cross it, the consumer threads that drain it, and the listeners that report queue depth and an underlying resource ...

Publishes session and message metrics to a Micrometer MeterRegistry the application supplies, so they reach whatever backend that registry is already bound to.