Features
- Best Message Delivery
- Bi-Directional
- Cascading Transport Layer
- Client Connectivity (Roundtrip Monitor)
- Client Driven Events
- Compression
- Conflation
- Firewall Compatible
- Guaranteed Message Delivery
- Hierarchical Topics
- High & Low Water Marks
- High Performance & Scalability
- Multiple Queue Types
- Multiple Message Types
- Multiple Transport Layers
- Secure
- Simple & Flexible API
- Technology Agnostic
- Topic Aliasing
- Web Sockets
- Zero Copy
- Zero Download
- Zero Fan Out Time
- Zero Latency
Diffusion has three types of client queues;
- FIFO
- SET
- User defined
As messages are published to the client they are placed in their queue until the client is ready to receive them.
FIFO (First In First Out)
Essentially, as the name suggests, each message is served to the client in the order they are published.
SET
The set queue type allows you to perform conflation (see Conflation), so on adding a message to the queue, it will check to see if a delta message for the same entity already exists. If so, then the first message will be superseded by the second and never published. This is really important technique for both ensuring the best possible experience for your clients (i.e. their machine isn’t swamped due to the message load) in environments where data volatility is high. Of course, even if you select this client queue type, you can still override this for given messages you don’t want to conflate.
User Defined
The out of the box queue types should cover, pretty well, all eventualities, but should your application need logic different to either, then implementing your own queue type is fairly straight forward.
