Message Formats and Content Filtering

📄️ Why should I use AMPS content filtering?

AMPS content filtering is like a swiss army knife -- there are dozens of ways to use it in an application.

📄️ What is the default message type for AMPS?

AMPS does not have a default message type. The AMPS server represents messages in one of two ways:

📄️ Does AMPS validate messages?

AMPS is designed for the highest possible performance. This means that AMPS does not parse (or validate) messages unless AMPS will use the results of parsing the message.

📄️ How does AMPS handle invalid FIX/NVFIX?

AMPS is designed to balance performance and flexibility. In most cases, AMPS does not guarantee specific behavior with invalid messages.

📄️ Can AMPS filters do case-insensitive comparisons?

Yes!

📄️ Can I just send uninterpreted binary messages with AMPS?

Yes. Starting in AMPS 4.0, AMPS includes a binary message type. This type allows you to send any type of content in the message payload. AMPS does not interpret the payload, so functions such as content filtering, SOW storage, aggregation, and so forth are not supported with this message type.

📄️ What's BFlat?

BFlat is intended to provide performance similar to FIX or NVFIX for binary data. It's a simple, non-hierarchical binary message format. BFlat is designed to be compact, self-describing, and very efficient to serialize and parse.