Skip to content

📚 Add docs for receiver thread & server responses (backport) #440

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 21, 2025

Conversation

nevans
Copy link
Collaborator

@nevans nevans commented Apr 21, 2025

Backports #418 (including tweak from #437) to v0.2-stable.

nevans added 2 commits April 20, 2025 21:28
Most importantly, this documents the scenarios that need extra care to
avoid memory leaks:
* Commands such as #list or #fetch can have an enormous number of
  responses.
* Commands such as #fetch can result in an enormous size per response.
* Long-lived connections will gradually accumulate unsolicited server
  responses, especially +EXISTS+, +FETCH+, and +EXPUNGE+ responses.
* A buggy or untrusted server could send inappropriate responses, which
  could be very numerous, very large, and very rapid.
@nevans nevans merged commit 8e2a847 into v0.2-stable Apr 21, 2025
14 checks passed
@nevans nevans deleted the backport/v0.2-document-response-limits branch April 21, 2025 02:37
@nevans nevans added documentation Improvements or additions to documentation backport This issue or PR is for a stable release branch labels Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport This issue or PR is for a stable release branch documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant