This mostly affects the RecommendedServerDiscovery rejecting servers not meeting the hardcoded minimum server version, but the option value can be used by the client too.
* add compatibility util to consume flows from Java
* add api changes
* Make JavaFlow static and tweak the behavior a bit
Co-authored-by: Niels van Velzen <git@ndat.nl>
- Add option to KtorClient to disable redirection following and set the connection timeout
- Uses the previous behavior by default
- Timeout is now 6 seconds by default (was 10)
- Throw exceptions for bad states in KtorClient
- InvalidStatusException - when the status is not in the 100-299 range
- TimeoutException - when the http request was not able to connect to the server within the timeout
- InvalidContentException - when the response is incorrect (different JSON schema)
The recommended version should always be the latest server version (which is stored in apiVersion). The minimumVersion should be the latest server version without significant API changes and is manually updated.