Tell me, is the initiative to create a stream on the side of the publisher or on the side of the subscriber?
I assumed that the subscriber makes a request for a stream of events, and waits for these events on a certain TCP port(or in separate thread/process) for a while.
But in the example given in the NoSQL distribution kit, everything is not so... The publisher in this example acts as if he were a subscriber at the same time.
How can I achieve a behavior, I described above: subscriber makes a request for a stream of events, and catch them when they occur?
Any help would be very appreciated.