Proposal to add maintained "Implementor notes"

[ktoso]

As more and more people start implementing this spec, confusion arrises on a few common spec points. For example distinguishing: hot / cold, persistent / (ephemeral / transient?) or unicast / multicast (fan-out?) is an exercise each implementor does on his own when they get to some point of their implementation...

I would like to propose we collect common terms like these used by implementors and maybe "hints" or "examples". The goal of this would be to be less strict than the spec, but give new implementors some food for thought etc. This could be either a wiki on reactive-streams/reactive-streams or another project that can be modified without the full cycle of voting that makes sense for the spec, but less so for such collection of notes.

Would there be interest to discuss and update such docs?

[viktorklang]

Interesting aspects:

losslessly backpressurizable or not? (where lossless == without dropping)
produces the same elements to each subscriber or not? (persistent/transient?)
multicast or unicast? (produces data independently or dependently to subscribers)

[viktorklang]

@ktoso I propose that this Issue is superseded by the new commented examples and #177, wdyt?

[ktoso]

I concur, 177 shares the same original goal I had in mind :)