forked from apache/tomcat
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathAdapter.java
More file actions
93 lines (84 loc) · 3.36 KB
/
Adapter.java
File metadata and controls
93 lines (84 loc) · 3.36 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.coyote;
import org.apache.tomcat.util.net.SocketStatus;
/**
* Adapter. This represents the entry point in a coyote-based servlet container.
*
*
* @author Remy Maucherat
* @see ProtocolHandler
*/
public interface Adapter {
/**
* Call the service method, and notify all listeners
*
* @param req The request object
* @param res The response object
*
* @exception Exception if an error happens during handling of
* the request. Common errors are:
* <ul><li>IOException if an input/output error occurs and we are
* processing an included servlet (otherwise it is swallowed and
* handled by the top level error handler mechanism)
* <li>ServletException if a servlet throws an exception and
* we are processing an included servlet (otherwise it is swallowed
* and handled by the top level error handler mechanism)
* </ul>
* Tomcat should be able to handle and log any other exception ( including
* runtime exceptions )
*/
public void service(Request req, Response res) throws Exception;
/**
* Prepare the given request/response for processing. This method requires
* that the request object has been populated with the information available
* from the HTTP headers.
*
* @param req The request object
* @param res The response object
*
* @return <code>true</code> if processing can continue, otherwise
* <code>false</code> in which case an appropriate error will have
* been set on the response
*
* @throws Exception If the processing fails unexpectedly
*/
public boolean prepare(Request req, Response res) throws Exception;
public boolean asyncDispatch(Request req,Response res, SocketStatus status)
throws Exception;
public void errorDispatch(Request request, Response response);
public void log(Request req, Response res, long time);
/**
* Assert that request and response have been recycled. If they have not
* then log a warning and force a recycle. This method is called as a safety
* check when a processor is being recycled and may be returned to a pool
* for reuse.
*
* @param req
* Request
* @param res
* Response
*/
public void checkRecycled(Request req, Response res);
/**
* Provide the name of the domain to use to register MBeans for components
* associated with the connector.
*
* @return The MBean domain name
*/
public String getDomain();
}