You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user is "giving " a buffer to the Multipart API, it's the responsibility of the MP API to close the user buffer. Now, to enforce transfer of resource ownership, maybe we should consider to use Send signatures in some of the Multipart API methods.
Maybe for example we could add the following:
A new __HttpPostMultipartRequestDecoder.offer(Send<HttpContent> content) method could be added , in addition to old HttpPostMultipartRequestDecoder.offer(HttpContent content)
This issue is related to the #1 PR.
When a user is "giving " a buffer to the Multipart API, it's the responsibility of the MP API to close the user buffer. Now, to enforce transfer of resource ownership, maybe we should consider to use Send signatures in some of the Multipart API methods.
Maybe for example we could add the following:
The text was updated successfully, but these errors were encountered: