Before this change, calling close after abort would raise an IOException. It's well-understood that streams should be closed after they're done being used. This was not possible before this change, if abort was called.
As a side effect of this change, abort now calls close on the underlying input stream. This is the behavior of the 1.x SDK, so it is low-risk.
Before this change, calling
close
afterabort
would raise an IOException. It's well-understood that streams should beclose
d after they're done being used. This was not possible before this change, ifabort
was called.As a side effect of this change,
abort
now callsclose
on the underlying input stream. This is the behavior of the 1.x SDK, so it is low-risk.