Example usage for org.apache.http.client HttpClient interface-usage

Introduction

In this page you can find the example usage for org.apache.http.client HttpClient interface-usage.

Usage

From source file org.jasig.cas.util.SimpleHttpClient.java

     * @param executorService The executor service to send messages to end points.
     */
    public void setExecutorService(@NotNull final ExecutorService executorService) {
        Assert.notNull(executorService);
        EXECUTOR_SERVICE = executorService;
    }

From source file org.vietspider.net.client.impl.AbstractHttpClient.java

/**
 * Convenience base class for HTTP client implementations.
 *
 * @author <a href="mailto:rolandw at apache.org">Roland Weber</a>
 * @author <a href="mailto:oleg at ural.ru">Oleg Kalnichevski</a>
 *

From source file com.apigee.sdk.apm.http.impl.client.cache.CachingHttpClient.java

/**
 * @since 4.1
 */
@ThreadSafe
// So long as the responseCache implementation is threadsafe
public class CachingHttpClient implements HttpClient {

From source file org.apache.http.impl.client.cache.CachingHttpClient.java

/**
 * <p>The {@link CachingHttpClient} is meant to be a drop-in replacement for
 * a {@link DefaultHttpClient} that transparently adds client-side caching.
 * The current implementation is conditionally compliant with HTTP/1.1
 * (meaning all the MUST and MUST NOTs are obeyed), although quite a lot,
 * though not all, of the SHOULDs and SHOULD NOTs are obeyed too. Generally

From source file de.tudarmstadt.ukp.shibhttpclient.ShibHttpClient.java

/**
 * Simple Shibbolethized {@link HttpClient} using basic HTTP username/password authentication to
 * authenticate against a predefined IdP. The client indicates its ECP capability to the SP.
 * Authentication happens automatically if the SP replies to any requesting using a PAOS
 * authentication solicitation.
 * <p>

From source file org.apache.http.impl.client.AbstractStatisticsGatheringHttpClient.java

/**
 * Base class for {@link HttpClient} implementations. This class acts as
 * a facade to a number of special purpose handler or strategy
 * implementations responsible for handling of a particular aspect of
 * the HTTP protocol such as redirect or authentication handling or
 * making decision about connection persistence and keep alive duration.