Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • between HARegionQueue and DACE (DispatchedAndCurrentEvents) objects (through the mis-named HARegionQueue.eventsMap)
  • between HARegion and the two kinds of entries it holds: <Position,Conflatable>, and  and <ThreadIdentifier,SequenceID>

In both cases, the Java Maps are depicted as associations in the diagram (the Map objects are not shown explicitly). So, for instance HARegionQueue.eventsMap is a Map. It's depicted as a 1-to-(0..1 per Position) association from HARegionQueue to Position. Similarly for HARegion to Conflatable and HARegion to SequenceID.

The diagram introduces two types not actually present in the Java code. Both are depicted as subtypes of Long: SequenceID to stand for an event's sequence id; and Position to stand for a position in a queue. In the source code these are both just Longs.

...

1. The server is providing an initial image to a performed (see HARegionQueue.giiQueue)
2. The server A client is initializing in the process of registering and its message dispatcher as part of cliesnt queue initialization logic (see CacheClientProxy.queuedEvents)/queue are not fully created and initialized

After these operations are completed, the temporary queues are drained and the event is added to the HARegionQueue. The diagrams below show the different put paths in detail.


Image RemovedImage Added

These diagrams show more detail around the special handling during client queue initialization or providing an initial image.



Image RemovedImage RemovedImage AddedImage Added

Delivering/Dispatching Events to Client:

...