Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Consider re-introducing ByteBufferPool.NON_POOLING constant #11956

Closed
lorban opened this issue Jun 25, 2024 · 1 comment · Fixed by #12325 or #12400
Closed

Consider re-introducing ByteBufferPool.NON_POOLING constant #11956

lorban opened this issue Jun 25, 2024 · 1 comment · Fixed by #12325 or #12400
Labels
Enhancement

Comments

@lorban
Copy link
Contributor

lorban commented Jun 25, 2024

Jetty version(s)
12.1.x

Enhancement Description
The constant ByteBufferPool.NON_POOLING pool has been replaced with new instances of the non-pooling pool everywhere it was used. We should consider re-introducing this constant.

See: #11801
gregw added a commit that referenced this issue Jun 25, 2024
@gregw
Fix #11956
efc2089
@gregw
Copy link
Contributor

gregw commented Jun 25, 2024

@lorban I thought I'd done this ... oh I have now!

@gregw gregw closed this as completed Jun 25, 2024
@github-project-automation github-project-automation bot moved this to ✅ Done in Jetty 12.1.0 Jun 25, 2024
@olamy olamy mentioned this issue Sep 29, 2024
Merged
@olamy olamy mentioned this issue Oct 17, 2024
Merged
@olamy olamy mentioned this issue Jan 31, 2025
Closed
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
Enhancement
Projects
Jetty 12.1.0
Status: ✅ Done
Milestone
No milestone
2 participants
@gregw @lorban