mobile/android/thirdparty/ch/boye/httpclientandroidlib/ConnectionReuseStrategy.java

changeset 0
6474c204b198
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/mobile/android/thirdparty/ch/boye/httpclientandroidlib/ConnectionReuseStrategy.java	Wed Dec 31 06:09:35 2014 +0100
     1.3 @@ -0,0 +1,70 @@
     1.4 +/*
     1.5 + * ====================================================================
     1.6 + * Licensed to the Apache Software Foundation (ASF) under one
     1.7 + * or more contributor license agreements.  See the NOTICE file
     1.8 + * distributed with this work for additional information
     1.9 + * regarding copyright ownership.  The ASF licenses this file
    1.10 + * to you under the Apache License, Version 2.0 (the
    1.11 + * "License"); you may not use this file except in compliance
    1.12 + * with the License.  You may obtain a copy of the License at
    1.13 + *
    1.14 + *   http://www.apache.org/licenses/LICENSE-2.0
    1.15 + *
    1.16 + * Unless required by applicable law or agreed to in writing,
    1.17 + * software distributed under the License is distributed on an
    1.18 + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    1.19 + * KIND, either express or implied.  See the License for the
    1.20 + * specific language governing permissions and limitations
    1.21 + * under the License.
    1.22 + * ====================================================================
    1.23 + *
    1.24 + * This software consists of voluntary contributions made by many
    1.25 + * individuals on behalf of the Apache Software Foundation.  For more
    1.26 + * information on the Apache Software Foundation, please see
    1.27 + * <http://www.apache.org/>.
    1.28 + *
    1.29 + */
    1.30 +
    1.31 +package ch.boye.httpclientandroidlib;
    1.32 +
    1.33 +import ch.boye.httpclientandroidlib.protocol.HttpContext;
    1.34 +
    1.35 +/**
    1.36 + * Interface for deciding whether a connection can be re-used for
    1.37 + * subsequent requests and should be kept alive.
    1.38 + * <p>
    1.39 + * Implementations of this interface must be thread-safe. Access to shared
    1.40 + * data must be synchronized as methods of this interface may be executed
    1.41 + * from multiple threads.
    1.42 + *
    1.43 + * @since 4.0
    1.44 + */
    1.45 +public interface ConnectionReuseStrategy {
    1.46 +
    1.47 +    /**
    1.48 +     * Decides whether a connection can be kept open after a request.
    1.49 +     * If this method returns <code>false</code>, the caller MUST
    1.50 +     * close the connection to correctly comply with the HTTP protocol.
    1.51 +     * If it returns <code>true</code>, the caller SHOULD attempt to
    1.52 +     * keep the connection open for reuse with another request.
    1.53 +     * <br/>
    1.54 +     * One can use the HTTP context to retrieve additional objects that
    1.55 +     * may be relevant for the keep-alive strategy: the actual HTTP
    1.56 +     * connection, the original HTTP request, target host if known,
    1.57 +     * number of times the connection has been reused already and so on.
    1.58 +     * <br/>
    1.59 +     * If the connection is already closed, <code>false</code> is returned.
    1.60 +     * The stale connection check MUST NOT be triggered by a
    1.61 +     * connection reuse strategy.
    1.62 +     *
    1.63 +     * @param response
    1.64 +     *          The last response received over that connection.
    1.65 +     * @param context   the context in which the connection is being
    1.66 +     *          used.
    1.67 +     *
    1.68 +     * @return <code>true</code> if the connection is allowed to be reused, or
    1.69 +     *         <code>false</code> if it MUST NOT be reused
    1.70 +     */
    1.71 +    boolean keepAlive(HttpResponse response, HttpContext context);
    1.72 +
    1.73 +}

mercurial