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.
Message recording and replication are supported, so long as no content filter is applied to the topic. AMPS does not need to interpret the payload to provide these services unless filtering is requested.
The binary message type is loaded by default as binary.
You can use this type in declarations just as you would any other message type (except in cases where AMPS would need to be able to parse the message type).
For example, on a transport that does not restrict message types, a client could connect to AMPS and provide binary messages using the connection string:
Last updated