Driver convergence (3/5): delete FlowSessionDriver + FlowDatagramDriver (keep FlowDriver) #99
Labels
No labels
blocks-others
breaking
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
license: clean
license: foxio
needs-fuzz
priority: P0
priority: P1
priority: P2
question
roadmap
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
marcpardo/flowscope#99
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Breaking. Part of #84 — see RFC
plans/175-driver-event-convergence-rfc.md(PR #96), §3.2 + Q1.FlowSessionDriverandFlowDatagramDriverare ~95% structural twins carrying 10 constructors each (the constructor explosion). Their single-parser convenience is subsumed byDriver<E>+ one slot; the reassembly-vs-noop distinction is already a builder choice (session_*vsdatagram_*registration).Tasks (resolved: delete, not deprecate)
FlowSessionDriver(session_driver.rs) +FlowDatagramDriver(datagram_driver.rs) and their 20 constructors.FlowDriveras the documented low-level run-to-completion primitive (issue guardrail). Optionally trim its 6 constructors tonew+with_config.SessionEventusage in these paths (tracked separately in the SessionEvent issue).recipes.mdsingle-parser recipe ->Driver<E>+ one slot).netring impact
Only
pcap_flow.rsinstantiates these (one file). Coordinate via the netring tracking issue.Acceptance
Types gone; single-parser recipe documented via
Driver<E>; full gates clean; CHANGELOG + migration recipe.Part of #84.