ReadonlyoptionsValidated immutable writer options.
ReadonlystoreOrdered storage receiving committed fragments.
Number of admitted and backpressured chunks still awaiting completion.
Tee stored fragments to a stream; a send failure stops later writes.
Abandon queued work immediately without persisting a store error status.
Stop teeing future stored fragments to a previously attached stream.
Enqueue a chunk and expose admission and persistence as separate promises.
Schedule the flush pump before the first write; safe to call repeatedly.
Write chunk as the final fragment and, unless told not to, close.
The chunk is enqueued before closure is asked for, and that order is the
whole of the synchronisation: the pump only starts its close once nothing
is outstanding, and admits whatever the bounded buffer held back before
that count reaches zero. So a close requested here cannot overtake the
chunk. With wait false the returned promise resolves immediately and both
are left to the pump; a failure is reported rather than dropped, and stays
visible through getStatus. AsyncNode.finalize is the entry
point application code wants -- it serializes values for you.
Requested abort/cancel status, or null for a graceful lifecycle.
Terminal status, or null while the writer remains open.
Whether ordinary writes can still be accepted.
Await all currently outstanding writes without closing the writer.
StaticcreateValidate options and create a writer over the supplied store.
Bounded, batched, stackless writer over a ChunkStore.
Producers enqueue chunks in logical sequence order. Await
admittedto respect queue backpressure andconfirmationto know storage accepted the fragment. The writer also callssendon attached wire streams; that call confirms local transport admission, not delivery by the remote agent.A final write fixes the logical end of the sequence. Lifecycle methods then either drain and seal storage, propagate an error, or cancel immediately.