There is a case: One part of the solution periodically publishes the data. This part is out of this article. There are two kind of subscribers. One kind of subscribers want to get the messages while they are published. Second kind of subscribers pool this messages randomly: undefined quantity of the subscribers request the undefined number times the LAST message in random interval. they want to get the last input message only. The usual publish-subscribe pattern doesn't work, because the usual subscriber...