michael@0: /*
michael@0:  * ====================================================================
michael@0:  * Licensed to the Apache Software Foundation (ASF) under one
michael@0:  * or more contributor license agreements.  See the NOTICE file
michael@0:  * distributed with this work for additional information
michael@0:  * regarding copyright ownership.  The ASF licenses this file
michael@0:  * to you under the Apache License, Version 2.0 (the
michael@0:  * "License"); you may not use this file except in compliance
michael@0:  * with the License.  You may obtain a copy of the License at
michael@0:  *
michael@0:  *   http://www.apache.org/licenses/LICENSE-2.0
michael@0:  *
michael@0:  * Unless required by applicable law or agreed to in writing,
michael@0:  * software distributed under the License is distributed on an
michael@0:  * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
michael@0:  * KIND, either express or implied.  See the License for the
michael@0:  * specific language governing permissions and limitations
michael@0:  * under the License.
michael@0:  * ====================================================================
michael@0:  *
michael@0:  * This software consists of voluntary contributions made by many
michael@0:  * individuals on behalf of the Apache Software Foundation.  For more
michael@0:  * information on the Apache Software Foundation, please see
michael@0:  * <http://www.apache.org/>.
michael@0:  *
michael@0:  */
michael@0: 
michael@0: package ch.boye.httpclientandroidlib.protocol;
michael@0: 
michael@0: import ch.boye.httpclientandroidlib.HttpRequestInterceptor;
michael@0: import ch.boye.httpclientandroidlib.HttpResponseInterceptor;
michael@0: 
michael@0: /**
michael@0:  * HTTP protocol processor is a collection of protocol interceptors that
michael@0:  * implements the 'Chain of Responsibility' pattern, where each individual
michael@0:  * protocol interceptor is expected to work on a particular aspect of the HTTP
michael@0:  * protocol the interceptor is responsible for.
michael@0:  * <p>
michael@0:  * Usually the order in which interceptors are executed should not matter as
michael@0:  * long as they do not depend on a particular state of the execution context.
michael@0:  * If protocol interceptors have interdependencies and therefore must be
michael@0:  * executed in a particular order, they should be added to the protocol
michael@0:  * processor in the same sequence as their expected execution order.
michael@0:  * <p>
michael@0:  * Protocol interceptors must be implemented as thread-safe. Similarly to
michael@0:  * servlets, protocol interceptors should not use instance variables unless
michael@0:  * access to those variables is synchronized.
michael@0:  *
michael@0:  * @since 4.0
michael@0:  */
michael@0: public interface HttpProcessor
michael@0:     extends HttpRequestInterceptor, HttpResponseInterceptor {
michael@0: 
michael@0:     // no additional methods
michael@0: }