| Modifier and Type | Class and Description |
|---|---|
class |
RealCall.AsyncCall |
Call.Factory| Modifier and Type | Field and Description |
|---|---|
Client |
client |
boolean |
forWebSocket |
Request |
originalRequest
The application's original request unadulterated by redirects or auth headers.
|
RetryAndFollowUpInterceptor |
retryAndFollowUpInterceptor |
AsyncTimeout |
timeout |
| Modifier and Type | Method and Description |
|---|---|
void |
cancel()
Cancels the request, if possible.
|
RealCall |
clone()
Create a new, identical call to this one which can be enqueued or executed even if this call
has already been.
|
void |
enqueue(Callback responseCallback)
Schedules the request to be executed at some point in the future.
|
Response |
execute()
Invokes the request immediately, and blocks until the response can be processed or is in
error.
|
boolean |
isCanceled() |
boolean |
isExecuted()
|
Request |
request() |
Timeout |
timeout()
Returns a timeout that spans the entire call: resolving DNS, connecting, writing the request
body, server processing, and reading the response body.
|
public final Client client
public final RetryAndFollowUpInterceptor retryAndFollowUpInterceptor
public final AsyncTimeout timeout
public final Request originalRequest
public final boolean forWebSocket
public Request request()
public Response execute() throws IOException
CallTo avoid leaking resources callers should close the Response which in turn will
close the underlying ResponseBody.
// ensure the response (and underlying response body) is closed
try (Response response = client.newCall(request).execute()) {
...
}
The caller may read the response body with the response's Response.body method. To
avoid leaking resources callers must close the response body or the
Response.
Note that transport-layer success (receiving a HTTP response code, headers and body) does
not necessarily indicate application-layer success: response may still indicate an
unhappy HTTP response code like 404 or 500.
execute in interface CallIOException - if the request could not be executed due to cancellation, a connectivity
problem or timeout. Because networks can fail during an exchange, it is possible that the
remote server accepted the request before the failure.public void enqueue(Callback responseCallback)
CallThe dispatcher defines when the request will run: usually
immediately unless there are several other requests currently being executed.
This client will later call back responseCallback with either an HTTP response or a
failure exception.
public void cancel()
Callpublic Timeout timeout()
CallConfigure the client's default timeout with Client.Builder.callTimeout.
public boolean isExecuted()
CallisExecuted in interface Callpublic boolean isCanceled()
isCanceled in interface CallCopyright © 2019. All rights reserved.