|
1 | 1 | Changelog
|
2 | 2 | ==========
|
3 | 3 |
|
| 4 | +Version 2.5.1 (17.02.2021) |
| 5 | +-------------------------- |
| 6 | + |
| 7 | +## Composer |
| 8 | + |
| 9 | +- Fix a case in `DataApiResponseAdapter` where an API call with a non-success result code being adapted to a `DataApiResponse` will result in the underlying `Response` and `Connection` not being closed (and potentially reused). |
| 10 | + |
4 | 11 | Version 2.5.0 (28.07.2020)
|
5 | 12 | --------------------------
|
6 | 13 |
|
7 | 14 | ## Client
|
8 | 15 |
|
9 |
| -- Deprecate `ResponseBody.writeTo()`, `ResponseBody.valuesBytes()`, |
10 |
| - `ResponseBody.valuesByteArray()`. |
| 16 | +- Deprecate `ResponseBody.writeTo()`, `ResponseBody.valuesBytes()`, `ResponseBody.valuesByteArray()`. |
11 | 17 |
|
12 |
| - The one-shot stream of data being held by a `ResponseBody` |
13 |
| - needs to be decoded by a `ProtocolReader` before use. `ResponseBody.reader()` |
14 |
| - returns such an instance which is already configured |
15 |
| - and ready for reading making these methods redundant. |
16 |
| - Also the aforementioned methods bring some behavior ambiguity in cases where |
17 |
| - the stream may be partially consumed through the exposed `ProtocolReader`. |
| 18 | + The one-shot stream of data being held by a `ResponseBody` needs to be decoded by a `ProtocolReader` before use. `ResponseBody.reader()` returns such an instance which is already configured and ready for reading making these methods redundant. |
| 19 | + Also the aforementioned methods bring some behavior ambiguity in cases where the stream may be partially consumed through the exposed `ProtocolReader`. |
18 | 20 |
|
19 |
| - **The methods will now throw an `IllegalStateException` if |
20 |
| - called when the response has been partially read via a `ProtocolReader`.** |
| 21 | + **The methods will now throw an `IllegalStateException` if called when the response has been partially read via a `ProtocolReader`.** |
21 | 22 |
|
22 | 23 | **The methods will be removed in the next major release of the library.**
|
23 | 24 |
|
24 |
| -- Fix potential connection leaks in `Call.enqueue()` |
25 |
| -and `Call.enqueueAndWait()` implementations. |
26 |
| -- Review connection closing/recycling in the `MultiCall` implementation |
27 |
| -- Add more assertions regarding connection recycling/closure in `Call`, |
28 |
| -`MultiCall` unit tests. |
| 25 | +- Fix potential connection leaks in `Call.enqueue()` and `Call.enqueueAndWait()` implementations. |
| 26 | +- Review connection closing/recycling in the `MultiCall` implementation. |
| 27 | +- Add more assertions regarding connection recycling/closure in `Call` and `MultiCall` unit tests. |
29 | 28 |
|
30 | 29 | Version 2.4.1 (20.03.2020)
|
31 | 30 | --------------------------
|
@@ -154,13 +153,13 @@ Version 2.0.0 (05.01.2018)
|
154 | 153 | * Internal optimizations in `BytesWriter` to minimize allocations
|
155 | 154 | * More unit tests for `BytesWriter`
|
156 | 155 | * ProtocolResponseReader can now directly read the data after data-enriched responses.
|
157 |
| -* Added the `SCOPE_DATA` scope in `ProtocolResponseReader` will be entered after all the values of a data-enriched response are read and the `ProtocolResponseReader` is at the begging of the attached data bytes. |
| 156 | +* Added the `SCOPE_DATA` scope in `ProtocolResponseReader` will be entered after all the values of a data-enriched response are read and the `ProtocolResponseReader` is at the begging of the attached data bytes. |
158 | 157 | * Add delegating implementations for `ProtocolReader`, `ProtocolResponseReader`, `ProtocolRequestWriter`and `ProtocolWriter`.
|
159 | 158 |
|
160 | 159 | #### Client
|
161 | 160 |
|
162 | 161 | * Add the `ApiChannel` low-level interface for writing and reading binary-encoded data to an API connection.
|
163 |
| - - This addition exposes the lowest possible level of detail when writing/reading messages from the API by still abstracting away the details of connection establishment, TLS handshaking and so on. |
| 162 | + - This addition exposes the lowest possible level of detail when writing/reading messages from the API by still abstracting away the details of connection establishment, TLS handshaking and so on. |
164 | 163 | - The interface allows for pipelining of requests and reading/writing on separate threads.
|
165 | 164 | - Instances of the interface can be opened via `PCloudApiClient.newChannel()`.
|
166 | 165 |
|
|
0 commit comments