Pluggable http server#76
Conversation
RomanEmreis
added
enhancement
RomanEmreis
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 26f8d675c9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Another round soon, please! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 671ca2be9c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Chef's kiss. ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cd6eecb6a9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. What shall we delve into next? ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
Summary
This PR decouples neva's Streamable HTTP transport from Volga and introduces a pluggable HTTP engine architecture.
The new
HttpEngineabstraction allows any Rust HTTP stack — including axum, hyper, actix-web, or custom transports — to integrate with neva while reusing the existing JSON-RPC pipeline, SSE replay/deduplication, batch execution, and request routing logic.As part of this refactor:
http-serveris now engine-agnostic and no longer pulls Volga automaticallyhttp-server-volgaprovides the previous Volga-backed behaviorserver-fullpreserves the old out-of-the-box experience for backwards compatibilitydispatch_*helpers were added to simplify adapter implementationsexamples/neva::auth::ClaimscontractThis change makes Streamable HTTP transport framework-independent while keeping protocol handling centralized inside neva.
⚠ Breaking Changes
The
http-serverfeature flag is now framework-agnostic and no longer includes the Volga HTTP stack automatically.Existing applications relying on the previous implicit Volga integration must migrate to either:
http-server-volgaserver-fullPrevious behavior:
New equivalent behavior:
or
Developers using only
http-serverare now expected to provide their own HTTP engine implementation via theHttpEnginetrait.Type
Checklist