Skip to content
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

Rework HTTP response logic to avoid allocation #238

Open
dead-claudia opened this issue Apr 29, 2023 · 0 comments
Open

Rework HTTP response logic to avoid allocation #238

dead-claudia opened this issue Apr 29, 2023 · 0 comments

Comments

@dead-claudia
Copy link

This builds on #48. My server is structured to use response templates, so it's very easy to avoid allocation.

I'd like to see a variant of request.respond(...) that doesn't require allocation (especially for headers), so I don't need to create an entire short-lived Vec just for headers. I was looking through the source code, and this seems very doable. The response logic just uses the Response object to respond directly without queueing anything. And the request.respond(response) method itself neither does any allocation nor does any queueing either.

@dead-claudia dead-claudia changed the title Rework responding to avoid allocation Rework HTTP response logic to avoid allocation Apr 29, 2023
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

No branches or pull requests

1 participant