Reactive Streams 1.0.0¶
Reactive Streams Special Interest Group. (2015). Reactive Streams 1.0.0.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Backpressure Signal
- … how long anyone waits, pair backpressure with an explicit shed/sample policy for sources that cannot comply, and remember the signal governs rate, not storage — the buffer that absorbs the residual is Bounded Mailbox or Queue's concern, and the two are complements, not substitutes.
This sourceReactive Streams uses demand signaling to constrain element flow; a source that cannot be backpressured must buffer or drop elements within bounds, so bounded buffering remains part of the design.
- … how long anyone waits, pair backpressure with an explicit shed/sample policy for sources that cannot comply, and remember the signal governs rate, not storage — the buffer that absorbs the residual is Bounded Mailbox or Queue's concern, and the two are complements, not substitutes.
- Flow Gate or Valve Rule
- Throttling an inflow propagates the constraint upstream as backpressure
This sourceDefines backpressure as demand signaling through which a slower subscriber propagates an intake constraint upstream.
- Throttling an inflow propagates the constraint upstream as backpressure
- Formation Throttle
- It is the natural mate of backpressure in flow-controlled systems: a formation throttle is simply backpressure applied at the source.
This sourceDefines Reactive Streams back pressure as demand signaled to an upstream publisher so production does not overwhelm downstream capacity.
- It is the natural mate of backpressure in flow-controlled systems: a formation throttle is simply backpressure applied at the source.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:929633a4a3ad · see in the full table