Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Asynchronous Http and WebSocket Client library for Java
craigwblake/async-http-client-1
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Sign In Required
Please sign in to use Codespaces.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching Xcode
If nothing happens, download Xcode and try again.
Launching Visual Studio Code
Your codespace will open once ready.
There was a problem preparing your codespace, please try again.
Latest commit
Git stats
Files
Failed to load latest commit information.
README.md
Async Http Client (@AsyncHttpClient on twitter)
Async Http Client library purpose is to allow Java applications to easily execute HTTP requests and asynchronously process the HTTP responses. The library also supports the WebSocket Protocol. The Async HTTP Client library is simple to use.
First, in order to add it to your Maven project, simply add this dependency:
dependency> groupId>com.ninggroupId> artifactId>async-http-clientartifactId> version>1.9.31version> dependency>
You can also download the artifact
AHC is an abstraction layer that can work on top of the bare JDK, Netty and Grizzly. Note that the JDK implementation is very limited and you should REALLY use the other real providers.
You then have to add the Netty or Grizzly jars in the classpath.
dependency> groupId>io.nettygroupId> artifactId>nettyartifactId> version>LATEST_NETTY_3_VERSIONversion> dependency>
dependency> groupId>org.glassfish.grizzlygroupId> artifactId>connection-poolartifactId> version>LATEST_GRIZZLY_VERSIONversion> dependency> dependency> groupId>org.glassfish.grizzlygroupId> artifactId>grizzly-websocketsartifactId> version>LATEST_GRIZZLY_VERSIONversion> dependency>
Check migration guide for migrating from 1.8 to 1.9.
Then in your code you can simply do
import com.ning.http.client.*; import java.util.concurrent.Future; AsyncHttpClient asyncHttpClient = new AsyncHttpClient(); FutureResponse> f = asyncHttpClient.prepareGet("http://www.ning.com/").execute(); Response r = f.get();
Note that in this case all the content must be read fully in memory, even if you used getResponseBodyAsStream() method on returned Response object.
You can also accomplish asynchronous (non-blocking) operation without using a Future if you want to receive and process the response in your handler:
import com.ning.http.client.*; import java.util.concurrent.Future; AsyncHttpClient asyncHttpClient = new AsyncHttpClient(); asyncHttpClient.prepareGet("http://www.ning.com/").execute(new AsyncCompletionHandlerResponse>()< @Override public Response onCompleted(Response response) throws Exception< // Do something with the Response // . return response; > @Override public void onThrowable(Throwable t)< // Something wrong happened. > >);
(this will also fully read Response in memory before calling onCompleted )
You can also mix Future with AsyncHandler to only retrieve part of the asynchronous response
import com.ning.http.client.*; import java.util.concurrent.Future; AsyncHttpClient asyncHttpClient = new AsyncHttpClient(); FutureInteger> f = asyncHttpClient.prepareGet("http://www.ning.com/").execute( new AsyncCompletionHandlerInteger>()< @Override public Integer onCompleted(Response response) throws Exception< // Do something with the Response return response.getStatusCode(); > @Override public void onThrowable(Throwable t)< // Something wrong happened. > >); int statusCode = f.get();
which is something you want to do for large responses: this way you can process content as soon as it becomes available, piece by piece, without having to buffer it all in memory.
You have full control on the Response life cycle, so you can decide at any moment to stop processing what the server is sending back:
import com.ning.http.client.*; import java.util.concurrent.Future; AsyncHttpClient c = new AsyncHttpClient(); FutureString> f = c.prepareGet("http://www.ning.com/").execute(new AsyncHandlerString>() < private ByteArrayOutputStream bytes = new ByteArrayOutputStream(); @Override public STATE onStatusReceived(HttpResponseStatus status) throws Exception < int statusCode = status.getStatusCode(); // The Status have been read // If you don't want to read the headers,body or stop processing the response if (statusCode >= 500) < return STATE.ABORT; > > @Override public STATE onHeadersReceived(HttpResponseHeaders h) throws Exception < Headers headers = h.getHeaders(); // The headers have been read // If you don't want to read the body, or stop processing the response return STATE.ABORT; > @Override public STATE onBodyPartReceived(HttpResponseBodyPart bodyPart) throws Exception < bytes.write(bodyPart.getBodyPartBytes()); return STATE.CONTINUE; > @Override public String onCompleted() throws Exception < // Will be invoked once the response has been fully read or a ResponseComplete exception // has been thrown. // NOTE: should probably use Content-Encoding from headers return bytes.toString("UTF-8"); > @Override public void onThrowable(Throwable t) < >>); String bodyResponse = f.get();
Finally, you can also configure the AsyncHttpClient via its AsyncHttpClientConfig object:
AsyncHttpClientConfig cf = new AsyncHttpClientConfig.Builder() S.setProxyServer(new ProxyServer("127.0.0.1", 38080)).build(); AsyncHttpClient c = new AsyncHttpClient(cf);
Async Http Client also support WebSocket by simply doing:
WebSocket websocket = c.prepareGet(getTargetUrl()) .execute(new WebSocketUpgradeHandler.Builder().addWebSocketListener( new WebSocketTextListener() < @Override public void onMessage(String message) < >@Override public void onOpen(WebSocket websocket) < websocket.sendTextMessage(". ").sendMessage(". "); > @Override public void onClose(WebSocket websocket) < latch.countDown(); > @Override public void onError(Throwable t) < >>).build()).get();
The library uses Java non blocking I/O for supporting asynchronous operations. The default asynchronous provider is build on top of Netty, but the library exposes a configurable provider SPI which allows to easily plug in other frameworks like Grizzly
AsyncHttpClientConfig config = new AsyncHttpClientConfig.Builder().build(); AsyncHttpClient client = new AsyncHttpClient(new GrizzlyAsyncHttpProvider(config), config);
Keep up to date on the library development by joining the Asynchronous HTTP Client discussion group
Of course, Pull Requests are welcome.
Here a the few rules we’d like you to respect if you do so:
- Only edit the code related to the suggested change, so DON’T automatically format the classes you’ve edited.
- Respect the formatting rules:
- Ident with 4 spaces
- Use a 140 chars line max length
- Don’t use * imports
- Stick to the org, com, javax, java imports order
- You must be the original author of the code you suggest.
- If not, you have to prove that the original code was published under Apache License 2 and properly mention original copyrights.
About
Asynchronous Http and WebSocket Client library for Java