feat: expose embeddable data HTTP service - #4
Merged
Merged
Conversation
- Add a cloneable DataService with direct request handling and a mountable Axum router. Reuse the standalone data path for parsing, deadlines, response validation and sanitized HTTP errors without opening listeners or exposing management routes. - Provide explicit shared Registry shutdown with incomplete-upload cancellation. Document host authorization, mount-prefix handling and lifecycle ownership, and cover embedding, encoding, errors, HEAD, deadlines and shutdown without sockets.
adamcavendish
force-pushed
the
feat/embedded-data-http
branch
from
September 16, 2026 06:25
9b0c546 to
c45a751
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
http::DataServicefor direct request handling or mounting an Axum router in a host, without binding SQLRest listeners.Documentation
README links to HTTP embedding instructions. The HTTP guide includes router/direct-handler integration and lifecycle boundaries; CHANGELOG records the feature under Unreleased.