flusso-queue-channel 0.10.1

In-process channel queue implementation for flusso.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

# flusso-queue-channel

An in-process work queue over a bounded `tokio` mpsc channel.

## At a glance

| | |
| --- | --- |
| **Constructor** | [`channel`]`(capacity)` → ([`ChannelProducer`], [`ChannelConsumer`]) |
| **Producer** | cloneable — publish from many tasks |
| **Consumer** | single — one per queue |
| **Backpressure** | `publish` waits when the channel is full |
| **Close** | drains and closes once every producer is dropped |
| **Ack** | no-op (nothing to make durable in memory) |

## How it works

[`channel`] returns a cloneable [`ChannelProducer`] and a single
[`ChannelConsumer`]. The bound gives backpressure — publishing waits when the
channel is full — and the queue closes and drains once every producer is
dropped.

Acknowledgement is a no-op: an in-memory channel has nothing to make durable.
Redelivery for the change pipeline comes from the source, not the channel —
the replication slot only advances once work is confirmed downstream. The
[`AckHandle`] surface is honored anyway, so the same engine loop runs unchanged
against a durable backend later.