Max channel size feature for consume request

[matthias-wende-sociomantic]

Some applications don't need to read all data all the time, e.g. testing applications or applications collecting data for short term analysis. For those it would be simpler if the channel wouldn't overflow and just keep the newest entries up to a certain size.

Another feature could be "remove channel on stop request", which would be of particular interests for application tests on production data in combination with the channel subscriber feature.

[gavin-norman-sociomantic]

We usually note such feature ideas in the proto repo, which is where the "public API" of the nodes is detailed (and is where the majority of the work would be).

[matthias-wende-sociomantic]

We usually note such feature ideas in the proto repo

makes sense