Skip to content

Remove the client-side courier getters - #70

Merged
david415 merged 1 commit into
mainfrom
remove-courier-getters
Jul 5, 2026
Merged

Remove the client-side courier getters#70
david415 merged 1 commit into
mainfrom
remove-courier-getters

Conversation

@david415

@david415 david415 commented Jul 5, 2026

Copy link
Copy Markdown
Member

The daemon owns courier selection and pins it across the two-phase ARQ receive and every retry, so a thin-client courier getter influences nothing: StartResendingEncryptedMessage carries no courier field. get_all_couriers, get_distinct_couriers, and get_courier_destination were leftovers from a pre-daemon-ARQ design; drop all three from the Rust and Python bindings and their tests.

The daemon owns courier selection and pins it across the two-phase ARQ receive
and every retry, so a thin-client courier getter influences nothing:
StartResendingEncryptedMessage carries no courier field. get_all_couriers,
get_distinct_couriers, and get_courier_destination were leftovers from a
pre-daemon-ARQ design; drop all three from the Rust and Python bindings and
their tests.
@david415
david415 merged commit ef2f1f7 into main Jul 5, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant