sqdv-delivery-cpp
暂无简介
- License 许可
- AGPL-3.0
- 所属仓库
- QuanuX/Symphony
- 最近更新
- 2026-11-14
- Stars
- ★ 2
- Forks
- 0
02 资源文件 17
- 其他cmake/SymphonySqdvDeliveryConfig.cmake.in463 B
- 其他cmake/uninstall.cmake.in216 B
- 参考文档CMakeLists.txt7.4 KB
- 参考文档FEATURES.md4.8 KB
- 其他include/symphony/sqdv/checkpoint.hpp2.2 KB
- 其他include/symphony/sqdv/delivery.hpp8.3 KB
- 参考文档INSTALL.md4.4 KB
- 参考文档INTENT.md1013 B
- 参考文档MANIFEST.md2.1 KB
- 参考文档SPEC.md19.0 KB
- 其他src/checkpoint.cpp10.9 KB
- 其他src/delivery.cpp30.4 KB
- 其他tests/checkpoint_test.cpp11.6 KB
- 其他tests/delivery_test.cpp37.6 KB
- 其他tests/package_lifecycle_test.cmake4.5 KB
- 参考文档tests/sdk-consumer/CMakeLists.txt454 B
- 其他tests/sdk-consumer/main.cpp17.5 KB
03 SKILL.md 正文
SQDV Delivery C++ Use
Purpose
Use the exact installed C++26 library for a caller-selected full-batch view and trusted same-process recipient. Read the installed SPEC before treating any processing, retention, or release event as evidence of another event.
Operation
- Resolve an exact SQMV manifest and configure one bounded SQFV context.
- Select
disposablefor caller-supplied live batches, or create/open aRetainedSourceusing the actual SQPV root and exact options forretained_before_delivery. All source and session handles share the one locked underlying store. - Create a
Sessionwith exact view/recipient/interface, partition, producer generation, initial sequence, and finite byte and processing limits. Supply an exact matching checkpoint only when resuming a caller-selected position. - Offer disposable batches directly. For retained delivery, commit through
RetainedSource::committo obtain an opaque verifiedRetainedBatch, then optionally offer that live candidate; the session reads the exact next retained sequence when the candidate is elsewhere or absent. - Take a
Delivery. Acknowledge processing in sequence when processing has actually completed. Independently release its payload when byte access is finished. Persist processed checkpoints through the caller's selected owner. - On an uncertain source outcome, preserve available processing progress, release payloads, close all source/session handles, and reopen the exact source. Resume with a matching checkpoint; old delivery tickets and old source proof handles cannot enter the new handle instance.
Scope
The library does not authorize recipients or prove source rights. Metadata classification, actual access authority, consumer processing assertions, local retention, external destination acceptance, and payload release remain separate. Discarding an unacknowledged ticket does not advance its session. Caller-owned resume persistence and replay policy determine handling of a lost checkpoint.
For durable resume, choose a private bounded CheckpointJournal and preserve its original baseline/generation. Use save_retained when source replay must cover processed progress. Handle limit/uncertainty explicitly; never promote processing acknowledgment into an external destination commit.