Skip to content

anemo: allow separate max_frame_size for requests and responses#11

Closed
aschran wants to merge 4 commits into
bmwill:mainfrom
MystenLabs:aschran/a1
Closed

anemo: allow separate max_frame_size for requests and responses#11
aschran wants to merge 4 commits into
bmwill:mainfrom
MystenLabs:aschran/a1

Conversation

@aschran
Copy link
Copy Markdown
Contributor

@aschran aschran commented Apr 28, 2026

Summary

  • Add max_request_frame_size and max_response_frame_size to Config. Each falls back to max_frame_size when unset, so existing configs behave identically.
  • Split the wire codec helper into request_message_frame_codec / response_message_frame_codec and wire them into the inbound/outbound stream codecs accordingly (server: recv = request codec, send = response codec; client: send = request codec, recv = response codec).

Test plan

  • cargo nextest run -p anemo --lib (80 tests pass, including 4 new config unit tests and 3 new end-to-end RPC tests covering the new options and the max_frame_size fallback)
  • cargo clippy --all-targets
  • cargo fmt --all -- --check

🤖 Generated with Claude Code

semenov-vladyslav and others added 4 commits March 18, 2025 14:19
Adds `max_request_frame_size` and `max_response_frame_size` Config
options. Each falls back to `max_frame_size` when unset, preserving
existing behavior.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@aschran aschran closed this Apr 28, 2026
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.

2 participants