onBackpressureBuffer is not chainable with onBackpressureDrop

[stevenzwu]

because it always requests Long.MAX_VALUE

[benjchristensen]

The reason is that onBackpressureBuffer and onBackpressureDrop both exist to handle sources that don't respect backpressure, hence request(Long.MAX_VALUE) since that is not relevant on a source that doesn't obey backpressure.

Chaining them though assumes they compose backpressure request(n) which they don't.

So the question is whether we make them compose request(n) backpressure despite normally not being needed so they can compose, or should we have an onBackpressure(Strategy s) or onBackpressureBufferThenDrop style operator?

[stevenzwu]

Just from usability point of view, composeable chaining is better than onBackpressureBufferThenDrop.
.onBackpressureDrop(onDrop).onBackpressureBuffer(capacity)

but looks like it's very difficult to chain with current assumption/implementation. btw these two, I like the first one, because it is more extensible: (1) onBackpressure(Strategy s) (2)onBackpressureBufferThenDrop

[akarnokd]

See #3487.

[akarnokd]

Fix released via 1.1.2.

I'm closing this issue due to inactivity. If you have further input on the issue, don't hesitate to reopen this issue or post a new one.