-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Jetty 12: review/remove ByteBufferPool #9166
Comments
I'm just adding my voice of caution here, that we did try to do this before, but found a few cases that were just too hard to use the stricter Note that I think we can change the API of |
1 similar comment
I'm just adding my voice of caution here, that we did try to do this before, but found a few cases that were just too hard to use the stricter Note that I think we can change the API of |
* Replaced usages of ByteBufferPool with RetainableByteBufferPool. * Removed ByteBufferPool and related classes. Signed-off-by: Simone Bordet <[email protected]>
Signed-off-by: Simone Bordet <[email protected]>
* Fixes #9166 - Jetty 12: review/remove ByteBufferPool * Replaced usages of ByteBufferPool with RetainableByteBufferPool. * Removed ByteBufferPool and related classes. * Renamed oej.http2.frames.DataFrame.getData() -> getByteBuffer() for consistency. * Removed Accumulator.acquire(), and updated code to use RetainableByteBufferPool.acquire() instead. * Fixed HttpOutput callbacks to correctly call super.onCompleteSuccess() and super.onCompleteFailure(). Signed-off-by: Simone Bordet <[email protected]>
Fixed by #9195. |
With issue jetty#9166, ByteBufferPool was removed and replaced by RetainableByteBufferPool. Since ByteBufferPool was used by AbstractConnector, this change broke backwards compatibility with third-party connectors such as junixsocket-jetty. Since there's no longer any other ByteBufferPool, rename the RetainableByteBufferPool interface, and thereby not only reinstate compatibility with existing third-party libraries but also save a few keystrokes. jetty#9284 Signed-off-by: Christian Kohlschütter <[email protected]>
With issue jetty#9166, ByteBufferPool was removed and replaced by RetainableByteBufferPool. Since ByteBufferPool was used by AbstractConnector, this change broke backwards compatibility with third-party connectors such as junixsocket-jetty. Since there's no longer any other ByteBufferPool, rename the RetainableByteBufferPool interface, and thereby not only reinstate compatibility with existing third-party libraries but also save a few keystrokes. jetty#9284 Signed-off-by: Christian Kohlschütter <[email protected]>
With issue jetty#9166, ByteBufferPool was removed and replaced by RetainableByteBufferPool. Since ByteBufferPool was used by AbstractConnector, this change broke backwards compatibility with third-party connectors such as junixsocket-jetty. Since there's no longer any other ByteBufferPool, rename the RetainableByteBufferPool interface, and thereby not only reinstate compatibility with existing third-party libraries but also save a few keystrokes. jetty#9284 Signed-off-by: Christian Kohlschütter <[email protected]>
Jetty version(s)
12
Description
The Jetty 12 code has now standardized to use
RetainableByteBufferPool
, soByteBufferPool
should be removed.This would simplify a lot the codebase, and also clean up the Jetty component tree, because now the
ByteBufferPool
s appear in the component tree, but not theRetainableByteBufferPool
s.This is a prerequisite for #9148, because it would then allow to inject leak-tracking
Pool
instances.The text was updated successfully, but these errors were encountered: