PreludeClientAsyncImpl

All Implemented Interfaces:: so.prelude.sdk.client.PreludeClientAsync


public final class PreludeClientAsyncImpl
 implements PreludeClientAsync

Nested Class Summary

Nested Classes
Modifier and Type	Class	Description
`public final class`	`PreludeClientAsyncImpl.WithRawResponseImpl`

Field Summary

Fields
Modifier and Type	Field	Description

Constructor Summary

Constructors
Constructor	Description
`PreludeClientAsyncImpl(ClientOptions clientOptions)`

Enum Constant Summary

Enum Constants
Enum Constant	Description

Method Summary

Modifier and Type	Method	Description
`PreludeClient`	`sync()`	Returns a version of this client that uses synchronous execution.
`PreludeClientAsync.WithRawResponse`	`withRawResponse()`	Returns a view of this service that provides access to raw HTTP responses for each method.
`TransactionalServiceAsync`	`transactional()`
`VerificationServiceAsync`	`verification()`
`WatchServiceAsync`	`watch()`
`Unit`	`close()`	Closes this client, relinquishing any underlying resources.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
  - PreludeClientAsyncImpl
```
PreludeClientAsyncImpl(ClientOptions clientOptions)
```
- Method Detail
  - sync
```
 PreludeClient sync()
```
    Returns a version of this client that uses synchronous execution.
    The returned client shares its resources, like its connection pool and thread pools, with this client.
  - withRawResponse
```
 PreludeClientAsync.WithRawResponse withRawResponse()
```
    Returns a view of this service that provides access to raw HTTP responses for each method.
  - transactional
```
 TransactionalServiceAsync transactional()
```
  - verification
```
 VerificationServiceAsync verification()
```
  - watch
```
 WatchServiceAsync watch()
```
  - close
```
 Unit close()
```
    Closes this client, relinquishing any underlying resources.
    This is purposefully not inherited from AutoCloseable because the client is long-lived and usually should not be synchronously closed via try-with-resources.
    It's also usually not necessary to call this method at all. the default HTTP client automatically releases threads and connections if they remain idle, but if you are writing an application that needs to aggressively release unused resources, then you may call this method.