Review DataBuffer handling code for proper release in case of error or cancellation [SPR-17408] #21941
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
Rossen Stoyanchev opened SPR-17408 and commented
Recent, related efforts on this topic include #21563, #21779, and #21322, but those changes needs some refinement plus a comprehensive review of all
DataBuffer
handling code with an eye towards error and cancellation signal cases.This is an umbrella ticket with sub-tasks:
DataBufferUtils
.ReactorServerHttpRequest
to drop the onDiscard hook.ClientHttpConnector
.For 4) and 5) above, perhaps we should consider inserting a common onDiscard at the point of using codecs to ensure consistent behavior? Of course individual codecs still need to be able to do the right thing on their own, but perhaps a hint could be passed in to indicate when onDiscard is handled externally..
Affects: 5.0.10, 5.1.1
Sub-tasks:
Issue Links:
Referenced from: commits 149d416, 488a1d4
The text was updated successfully, but these errors were encountered: