You can set
myTable.setRequestedMaxFrequency("unfiltered");
on the client page to ensure that none of the update events is filtered by the Server;
this causes the Server to enqueue the events, if needed.
Even if you don't use the above setting, the Server enqueues the update events rather than filtering them, as long as there is buffer space available.
While in MERGE mode the default buffer size is 1, in DISTINCT mode it is the maximum possible.
You can force filtering in DISTINCT mode by explicitly reducing the buffer, through
myTable.setRequestedBufferSize(5)
for instance.
In Moderato edition, an upper limit of one update per second is forced on the frequency for all items,
hence, for items with a source update frequency higher than that,
you can't help but either filtering or enqueueing.
If the source update frequency were steadily above one per second, then enqueueing would not be an option,
as the buffer would fill up and you would get delayed, yet filtered, updates.
In that case, setting a buffer size of 1 would be the only option.
