MessageAssociator
keeps the cache of recently sent message IDs and IDs of their original messages. The size of the cache is configurable through maximum message count and decay interval. The former limits the maximum cache size and the latter should reduce the cache size if bridge activity reduces.
Messages are associated by their association ID (or assocID) that consists of port name and message ID. Normally this is enough to keep these IDs unique and also allow normal bridge operation. If it turns out that there are cases where assocID uniqueness must be weakened (or strengthened) a way to deal with them would be to implement configurable assocID namespaces that are currently hardcoded to the name of a port defined in configuration.
MessageAssociator
only manages a cache of assocIDs which is neither complete nor persistent. However it can be integrated with a backing store that will be dynamically populated with new associations and queried for older entries that cannot be found in the cache.
@author Baltic Amadeus, JSC
@author Antanas Kompanas
|
|
|
|
|
|
|
|
|
|