Skip to content

Record that the spawned connection mode is built on the scoped spawn proposed for base-scheduler 0.6. - #83

Merged
ioquatix merged 1 commit into
mainfrom
spawned-mode-scoped-spawn
Nov 21, 2026
Merged

ioquatix merged 1 commit into
mainfrom
spawned-mode-scoped-spawn

Conversation

@ioquatix

Copy link
Copy Markdown
Contributor

Record in design/client-connection.md and M6 of design/roadmap.md the decision of 2026-11-21 that the opt-in spawned mode, in which each connection is its own task, uses the scoped spawn proposed in base-rs/base-scheduler#134 rather than Spawn's 'static tasks: the application runs its program inside a blocking scope, so connection tasks may borrow the scheduler and keep the scoped mode's lifetimes, with handlers bound to the scope and request bodies that outlive it, and a spawned server can forward a body through a spawned client. The notes record the rejected alternatives, a scheduler borrowed for 'static and reader and writer handles that own their scheduler, and that the spawned mode waits for scheduler 0.6.

@ioquatix
ioquatix merged commit e5ec21c into main Nov 21, 2026
8 checks passed
@ioquatix
ioquatix deleted the spawned-mode-scoped-spawn branch November 21, 2026 00:49
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