httpclient-4.0.2最新教程

HttpClient Tutorial

Oleg Kalnichevski

Preface (iv)

1. HttpClient scope (iv)

2. What HttpClient is NOT (iv)

1. Fundamentals (1)

1.1. Request execution (1)

1.1.1. HTTP request (1)

1.1.2. HTTP response (2)

1.1.3. Working with message headers (2)

1.1.4. HTTP entity (4)

1.1.5. Ensuring release of low level resources (5)

1.1.6. Consuming entity content (5)

1.1.7. Producing entity content (6)

1.1.8. Response handlers (7)

1.2. HTTP execution context (8)

1.3. Exception handling (9)

1.3.1. HTTP transport safety (9)

1.3.2. Idempotent methods (9)

1.3.3. Automatic exception recovery (10)

1.3.4. Request retry handler (10)

1.4. Aborting requests (11)

1.5. HTTP protocol interceptors (11)

1.6. HTTP parameters (12)

1.6.1. Parameter hierarchies (12)

1.6.2. HTTP parameters beans (13)

1.7. HTTP request execution parameters (13)

2. Connection management (15)

2.1. Connection parameters (15)

2.2. Connection persistence (16)

2.3. HTTP connection routing (16)

2.3.1. Route computation (16)

2.3.2. Secure HTTP connections (17)

2.4. HTTP route parameters (17)

2.5. Socket factories (17)

2.5.1. Secure socket layering (18)

2.5.2. SSL/TLS customization (18)

2.5.3. Hostname verification (18)

2.6. Protocol schemes (19)

2.7. HttpClient proxy configuration (19)

2.8. HTTP connection managers (20)

2.8.1. Connection operators (20)

2.8.2. Managed connections and connection managers (20)

2.8.3. Simple connection manager (22)

2.8.4. Pooling connection manager (22)

2.8.5. Connection manager shutdown (23)

2.9. Connection management parameters (23)

2.10. Multithreaded request execution (23)

2.11. Connection eviction policy (24)

2.12. Connection keep alive strategy (25)

3. HTTP state management (27)

HttpClient Tutorial

3.1. HTTP cookies (27)

3.1.1. Cookie versions (27)

3.2. Cookie specifications (28)

3.3. HTTP cookie and state management parameters (29)

3.4. Cookie specification registry (29)

3.5. Choosing cookie policy (29)

3.6. Custom cookie policy (30)

3.7. Cookie persistence (30)

3.8. HTTP state management and execution context (30)

3.9. Per user / thread state management (31)

4. HTTP authentication (32)

4.1. User credentials (32)

4.2. Authentication schemes (32)

4.3. HTTP authentication parameters (33)

4.4. Authentication scheme registry (33)

4.5. Credentials provider (33)

4.6. HTTP authentication and execution context (34)

4.7. Preemptive authentication (35)

4.8. NTLM Authentication (36)

4.8.1. NTLM connection persistence (36)

5. HTTP client service (38)

5.1. HttpClient facade (38)

5.2. HttpClient parameters (39)

5.3. Automcatic redirect handling (39)

5.4. HTTP client and execution context (40)

6. Advanced topics (41)

6.1. Custom client connections (41)

6.2. Stateful HTTP connections (42)

6.2.1. User token handler (42)

6.2.2. User token and execution context (43)

Preface

The Hyper-Text Transfer Protocol (HTTP) is perhaps the most significant protocol used on the Internet today. Web services, network-enabled appliances and the growth of network computing continue to expand the role of the HTTP protocol beyond user-driven web browsers, while increasing the number of applications that require HTTP support.

Although the https://www.sodocs.net/doc/6916747511.html, package provides basic functionality for accessing resources via HTTP, it doesn't provide the full flexibility or functionality needed by many applications. HttpClient seeks to fill this void by providing an efficient, up-to-date, and feature-rich package implementing the client side of the most recent HTTP standards and recommendations.

Designed for extension while providing robust support for the base HTTP protocol, HttpClient may be of interest to anyone building HTTP-aware client applications such as web browsers, web service clients, or systems that leverage or extend the HTTP protocol for distributed communication.

1. HttpClient scope

?Client-side HTTP transport library based on HttpCore [https://www.sodocs.net/doc/6916747511.html,/httpcomponents-core/

index.html]

?Based on classic (blocking) I/O

?Content agnostic

2. What HttpClient is NOT

?HttpClient is NOT a browser. It is a client side HTTP transport library. HttpClient's purpose is

to transmit and receive HTTP messages. HttpClient will not attempt to cache content, execute

javascript embedded in HTML pages, try to guess content type, or reformat request / redirect location

URIs, or other functionality unrelated to the HTTP transport.

Chapter 1. Fundamentals

1.1. Request execution

The most essential function of HttpClient is to execute HTTP methods. Execution of an HTTP method involves one or several HTTP request / HTTP response exchanges, usually handled internally by HttpClient. The user is expected to provide a request object to execute and HttpClient is expected to transmit the request to the target server return a corresponding response object, or throw an exception if execution was unsuccessful.

Quite naturally, the main entry point of the HttpClient API is the HttpClient interface that defines the contract described above.

Here is an example of request execution process in its simplest form:

1.1.1. HTTP request

All HTTP requests have a request line consisting a method name, a request URI and a HTTP protocol version.

HttpClient supports out of the box all HTTP methods defined in the HTTP/1.1 specification: GET, HEAD, POST, PUT, DELETE, TRACE and OPTIONS. There is a special class for each method type.: HttpGet, HttpHead, HttpPost, HttpPut, HttpDelete, HttpTrace, and HttpOptions.

The Request-URI is a Uniform Resource Identifier that identifies the resource upon which to apply the request. HTTP request URIs consist of a protocol scheme, host name, optional port, resource path, optional query, and optional fragment.

HttpClient provides a number of utility methods to simplify creation and modification of request URIs.

URI can be assembled programmatically:

stdout >

Query string can also be generated from individual parameters:

stdout >

1.1.

2. HTTP response

HTTP response is a message sent by the server back to the client after having received and interpreted

a request message. The first line of that message consists of the protocol version followed by a numeric

status code and its associated textual phrase.

stdout >

1.1.3. Working with message headers

An HTTP message can contain a number of headers describing properties of the message such as the content length, content type and so on. HttpClient provides methods to retrieve, add, remove and enumerate headers.

stdout >

The most efficient way to obtain all headers of a given type is by using the HeaderIterator interface.

stdout >

It also provides convenience methods to parse HTTP messages into individual header elements.

stdout >

1.1.4. HTTP entity

HTTP messages can carry a content entity associated with the request or response. Entities can be found in some requests and in some responses, as they are optional. Requests that use entities are referred to as entity enclosing requests. The HTTP specification defines two entity enclosing methods: POST and PUT. Responses are usually expected to enclose a content entity. There are exceptions to this rule such as responses to HEAD method and 204 No Content, 304 Not Modified, 205 Reset Content responses.

HttpClient distinguishes three kinds of entities, depending on where their content originates:

?streamed: The content is received from a stream, or generated on the fly. In particular, this

category includes entities being received from HTTP responses. Streamed entities are generally not

repeatable.

?self-contained: The content is in memory or obtained by means that are independent from a

connection or other entity. Self-contained entities are generally repeatable. This type of entities will

be mostly used for entity enclosing HTTP requests.

?wrapping: The content is obtained from another entity.

This distinction is important for connection management when streaming out content from an HTTP response. For request entities that are created by an application and only sent using HttpClient, the difference between streamed and self-contained is of little importance. In that case, it is suggested to consider non-repeatable entities as streamed, and those that are repeatable as self-contained.

1.1.4.1. Repeatable entities

An entity can be repeatable, meaning its content can be read more than once. This is only possible with self contained entities (like ByteArrayEntity or StringEntity)

1.1.4.

2. Using HTTP entities

Since an entity can represent both binary and character content, it has support for character encodings (to support the latter, ie. character content).

The entity is created when executing a request with enclosed content or when the request was successful and the response body is used to send the result back to the client.

To read the content from the entity, one can either retrieve the input stream via the HttpEntity#getContent() method, which returns an java.io.InputStream, or one can supply an output stream to the HttpEntity#writeTo(OutputStream) method, which will return once all content has been written to the given stream.

When the entity has been received with an incoming message, the methods HttpEntity#getContentType()and HttpEntity#getContentLength()methods can be used for reading the common metadata such as Content-Type and Content-Length headers (if they are available). Since the Content-Type header can contain a character encoding for text mime-types like text/plain or text/html, the HttpEntity#getContentEncoding()method is used to read this information. If the headers aren't available, a length of -1 will be returned, and NULL for the content type. If the Content-Type header is available, a Header object will be returned.

When creating an entity for a outgoing message, this meta data has to be supplied by the creator of the entity.

stdout >

1.1.5. Ensuring release of low level resources

When finished with a response entity, it's important to ensure that all entity content has been fully consumed, so that the connection could be safely returned to the connection pool and re-used by the connection manager for subsequent requests. The easiest way to do so is to call the HttpEntity#consumeContent() method to consume any available content on the stream. HttpClient will automatically release the underlying connection back to the connection manager as soon as it detects that the end of the content stream has been reached. The HttpEntity#consumeContent() method is safe to call more than once.

There can be situations, however, when only a small portion of the entire response content needs to be retrieved and the performance penalty for consuming the remaining content and making the connection reusable is too high, one can simply terminate the request by calling HttpUriRequest#abort() method.

The connection will not be reused, but all level resources held by it will be correctly deallocated.

1.1.6. Consuming entity content

The recommended way to consume content of an entity is by using its HttpEntity#getContent() or HttpEntity#writeTo(OutputStream) methods. HttpClient also comes with the EntityUtils class, which exposes several static methods to more easily read the content or information from an entity.

Instead of reading the java.io.InputStream directly, one can retrieve the whole content body in a string / byte array by using the methods from this class. However, the use of EntityUtils is strongly

discouraged unless the response entities originate from a trusted HTTP server and are known to be of limited length.

In some situations it may be necessary to be able to read entity content more than once. In this case entity content must be buffered in some way, either in memory or on disk. The simplest way to accomplish that is by wrapping the original entity with the BufferedHttpEntity class. This will cause the content of the original entity to be read into a in-memory buffer. In all other ways the entity wrapper will be have the original one.

1.1.7. Producing entity content

HttpClient provides several classes that can be used to efficiently stream out content though HTTP connections. Instances of those classes can be associated with entity enclosing requests such as POST and PUT in order to enclose entity content into outgoing HTTP requests. HttpClient provides several classes for most common data containers such as string, byte array, input stream, and file: StringEntity, ByteArrayEntity, InputStreamEntity, and FileEntity.

Please note InputStreamEntity is not repeatable, because it can only read from the underlying data stream once. Generally it is recommended to implement a custom HttpEntity class which is self-contained instead of using generic InputStreamEntity. FileEntity can be a good starting point.

1.1.7.1. Dynamic content entities

Often HTTP entities need to be generated dynamically based a particular execution context. HttpClient provides support for dynamic entities by using EntityTemplate entity class and ContentProducer interface. Content producers are objects which produce their content on demand, by writing it out to an output stream. They are expected to be able produce their content every time they are requested to do so. So entities created with EntityTemplate are generally self-contained and repeatable.

1.1.7.

2. HTML forms

Many applications frequently need to simulate the process of submitting an HTML form, for instance, in order to log in to a web application or submit input data. HttpClient provides special entity class UrlEncodedFormEntity to facilitate the process.

This UrlEncodedFormEntity instance will use the so called URL encoding to encode parameters and produce the following content:

1.1.7.3. Content chunking

Generally it is recommended to let HttpClient choose the most appropriate transfer encoding based on the properties of the HTTP message being transferred. It is possible, however, to inform HttpClient that the chunk coding is preferred by setting HttpEntity#setChunked() to true. Please note that HttpClient will use this flag as a hint only. This value well be ignored when using HTTP protocol versions that do not support chunk coding, such as HTTP/1.0.

1.1.8. Response handlers

The simplest and the most convenient way to handle responses is by using ResponseHandler interface.

This method completely relieves the user from having to worry about connection management. When using a ResponseHandler HttpClient will automatically take care of ensuring release of the connection back to the connection manager regardless whether the request execution succeeds or causes an exception.

1.2. HTTP execution context

Originally HTTP has been designed as a stateless, response-request oriented protocol. However, real world applications often need to be able to persist state information through several logically related request-response exchanges. In order to enable applications to maintain a processing state HttpClient allows HTTP requests to be executed within a particular execution context, referred to as HTTP context. Multiple logically related requests can participate in a logical session if the same context is reused between consecutive requests. HTTP context functions similarly to java.util.Map. It is simply a collection of arbitrary named values. Application can populate context attributes prior to a request execution or examine the context after the execution has been completed.

In the course of HTTP request execution HttpClient adds the following attributes to the execution context:

?'http.connection': HttpConnection instance representing the actual connection to the target

server.

?'http.target_host': HttpHost instance representing the connection target.

?'http.proxy_host': HttpHost instance representing the connection proxy, if used

?'http.request': HttpRequest instance representing the actual HTTP request.

?'http.response': HttpResponse instance representing the actual HTTP response.

?'http.request_sent': https://www.sodocs.net/doc/6916747511.html,ng.Boolean object representing the flag indicating whether the

actual request has been fully transmitted to the connection target.

For instance, in order to determine the final redirect target, one can examine the value of the http.target_host attribute after the request execution:

stdout >

1.3. Exception handling

HttpClient can throw two types of exceptions: java.io.IOException in case of an I/O failure such as socket timeout or an socket reset and HttpException that signals an HTTP failure such as a violation of the HTTP protocol. Usually I/O errors are considered non-fatal and recoverable, whereas HTTP protocol errors are considered fatal and cannot be automatically recovered from.

1.3.1. HTTP transport safety

It is important to understand that the HTTP protocol is not well suited for all types of applications.

HTTP is a simple request/response oriented protocol which was initially designed to support static or dynamically generated content retrieval. It has never been intended to support transactional operations.

For instance, the HTTP server will consider its part of the contract fulfilled if it succeeds in receiving and processing the request, generating a response and sending a status code back to the client. The server will make no attempts to roll back the transaction if the client fails to receive the response in its entirety due to a read timeout, a request cancellation or a system crash. If the client decides to retry the same request, the server will inevitably end up executing the same transaction more than once. In some cases this may lead to application data corruption or inconsistent application state.

Even though HTTP has never been designed to support transactional processing, it can still be used as a transport protocol for mission critical applications provided certain conditions are met. To ensure HTTP transport layer safety the system must ensure the idempotency of HTTP methods on the application layer.

1.3.

2. Idempotent methods

HTTP/1.1 specification defines idempotent method as

[Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N > 0 identical requests is the same as for a single request]

In other words the application ought to ensure that it is prepared to deal with the implications of multiple execution of the same method. This can be achieved, for instance, by providing a unique transaction id and by other means of avoiding execution of the same logical operation.

Please note that this problem is not specific to HttpClient. Browser based applications are subject to exactly the same issues related to HTTP methods non-idempotency.

HttpClient assumes non-entity enclosing methods such as GET and HEAD to be idempotent and entity enclosing methods such as POST and PUT to be not.

1.3.3. Automatic exception recovery

By default HttpClient attempts to automatically recover from I/O exceptions. The default auto-recovery mechanism is limited to just a few exceptions that are known to be safe.

?HttpClient will make no attempt to recover from any logical or HTTP protocol errors (those derived

from HttpException class).

?HttpClient will automatically retry those methods that are assumed to be idempotent.

?HttpClient will automatically retry those methods that fail with a transport exception while the HTTP

request is still being transmitted to the target server (i.e. the request has not been fully transmitted

to the server).

?HttpClient will automatically retry those methods that have been fully transmitted to the server,

but the server failed to respond with an HTTP status code (the server simply drops the connection

without sending anything back). In this case it is assumed that the request has not been processed by

the server and the application state has not changed. If this assumption may not hold true for the web

server your application is targeting it is highly recommended to provide a custom exception handler.

1.3.4. Request retry handler

In order to enable a custom exception recovery mechanism one should provide an implementation of the HttpRequestRetryHandler interface.

1.4. Aborting requests

In some situations HTTP request execution fail to complete within the expected time frame due to high load on the target server or too many concurrent requests issued on the client side. In such cases it may be necessary to terminate the request prematurely and unblock the execution thread blocked in a I/O operation. HTTP requests being executed by HttpClient can be aborted at any stage of execution by invoking HttpUriRequest#abort() method. This method is thread-safe and can be called from any thread. When an HTTP request is aborted its execution thread blocked in an I/O operation is guaranteed to unblock by throwing a InterruptedIOException

1.5. HTTP protocol interceptors

HTTP protocol interceptor is a routine that implements a specific aspect of the HTTP protocol. Usually protocol interceptors are expected to act upon one specific header or a group of related headers of the incoming message or populate the outgoing message with one specific header or a group of related headers. Protocol interceptors can also manipulate content entities enclosed with messages, transparent content compression / decompression being a good example. Usually this is accomplished by using the 'Decorator' pattern where a wrapper entity class is used to decorate the original entity. Several protocol interceptors can be combined to form one logical unit.

Protocol interceptors can collaborate by sharing information - such as a processing state - through the HTTP execution context. Protocol interceptors can use HTTP context to store a processing state for one request or several consecutive requests.

Usually the order in which interceptors are executed should not matter as long as they do not depend on

a particular state of the execution context. If protocol interceptors have interdependencies and therefore

must be executed in a particular order, they should be added to the protocol processor in the same sequence as their expected execution order.

Protocol interceptors must be implemented as thread-safe. Similarly to servlets, protocol interceptors should not use instance variables unless access to those variables is synchronized.

This is an example of how local context can be used to persist a processing state between consecutive requests:

1.6. HTTP parameters

HttpParams interface represents a collection of immutable values that define a runtime behavior of a component. In many ways HttpParams is similar to HttpContext. The main distinction between the two lies in their use at runtime. Both interfaces represent a collection of objects that are organized as

a map of keys to object values, but serve distinct purposes:

?HttpParams is intended to contain simple objects: integers, doubles, strings, collections and objects

that remain immutable at runtime.

?HttpParams is expected to be used in the 'write once - ready many' mode. HttpContext is intended

to contain complex objects that are very likely to mutate in the course of HTTP message processing.

?The purpose of HttpParams is to define a behavior of other components. Usually each complex

component has its own HttpParams object. The purpose of HttpContext is to represent an execution

state of an HTTP process. Usually the same execution context is shared among many collaborating

objects.

1.6.1. Parameter hierarchies

In the course of HTTP request execution HttpParams of the HttpRequest object are linked together with HttpParams of the HttpClient instance used to execute the request. This enables parameters set at the HTTP request level take precedence over HttpParams set at the HTTP client level. The recommended practice is to set common parameters shared by all HTTP requests at the HTTP client level and selectively override specific parameters at the HTTP request level.

stdout >

1.6.

2. HTTP parameters beans

HttpParams interface allows for a great deal of flexibility in handling configuration of components.

Most importantly, new parameters can be introduced without affecting binary compatibility with older versions. However, HttpParams also has a certain disadvantage compared to regular Java beans: HttpParams cannot be assembled using a DI framework. To mitigate the limitation, HttpClient includes

a number of bean classes that can used in order to initialize HttpParams objects using standard Java

bean conventions.

stdout >

1.7. HTTP request execution parameters

These are parameters that can impact the process of request execution:

?'http.protocol.version': defines HTTP protocol version used if not set explicitly on the request

object. This parameter expects a value of type ProtocolVersion. If this parameter is not set

HTTP/1.1 will be used.

?'http.protocol.element-charset': defines the charset to be used for encoding HTTP protocol

elements. This parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.String. If this parameter is not set US-

ASCII will be used.

?'http.protocol.content-charset': defines the charset to be used per default for content body coding. This parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.String. If this parameter is not set ISO-8859-1 will be used.

?'https://www.sodocs.net/doc/6916747511.html,eragent': defines the content of the User-Agent header. This parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.String. If this parameter is not set, HttpClient will automatically generate a value for it.

?'http.protocol.strict-transfer-encoding': defines whether responses with an invalid Transfer-Encoding header should be rejected. This parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.Boolean. If this parameter is not set invalid Transfer-Encoding values will be ignored.

?'http.protocol.expect-continue': activates Expect: 100-Continue handshake for the entity enclosing methods. The purpose of the Expect: 100-Continue handshake is to allow the client that is sending a request message with a request body to determine if the origin server is willing to accept the request (based on the request headers) before the client sends the request body. The use of the Expect: 100-continue handshake can result in a noticeable performance improvement for entity enclosing requests (such as POST and PUT) that require the target server's authentication. Expect: 100-continue handshake should be used with caution, as it may cause problems with HTTP servers and proxies that do not support HTTP/1.1 protocol. This parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.Boolean. If this parameter is not set HttpClient will attempt to use the handshake.

?'http.protocol.wait-for-continue': defines the maximum period of time in milliseconds the client should spend waiting for a 100-continue response. This parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.Integer. If this parameter is not set HttpClient will wait 3 seconds for a confirmation before resuming the transmission of the request body.

Chapter 2. Connection management

HttpClient has a complete control over the process of connection initialization and termination as well as I/O operations on active connections. However various aspects of connection operations can be controlled using a number of parameters.

2.1. Connection parameters

These are parameters that can influence connection operations:

?'http.socket.timeout': defines the socket timeout (SO_TIMEOUT) in milliseconds, which is

the timeout for waiting for data or, put differently, a maximum period inactivity between two

consecutive data packets). A timeout value of zero is interpreted as an infinite timeout. This

parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.Integer. If this parameter is not set read operations

will not time out (infinite timeout).

'http.tcp.nodelay': determines whether Nagle's algorithm is to be used. The Nagle's algorithm

tries to conserve bandwidth by minimizing the number of segments that are sent. When applications

wish to decrease network latency and increase performance, they can disable Nagle's algorithm (that

is enable TCP_NODELAY. Data will be sent earlier, at the cost of an increase in bandwidth consumption.

This parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.Boolean. If this parameter is not, TCP_NODELAY

will be enabled (no delay).

'http.socket.buffer-size': determines the size of the internal socket buffer used to buffer

data while receiving / transmitting HTTP messages. This parameter expects a value of type

https://www.sodocs.net/doc/6916747511.html,ng.Integer. If this parameter is not set HttpClient will allocate 8192 byte socket buffers.

'http.socket.linger': sets SO_LINGER with the specified linger time in seconds. The maximum

timeout value is platform specific. Value 0 implies that the option is disabled. Value -1 implies that

the JRE default is used. The setting only affects the socket close operation. If this parameter is not

set value -1 (JRE default) will be assumed.

'http.connection.timeout': determines the timeout in milliseconds until a connection is

established. A timeout value of zero is interpreted as an infinite timeout. This parameter expects a

value of type https://www.sodocs.net/doc/6916747511.html,ng.Integer. If this parameter is not set connect operations will not time out

(infinite timeout).

'http.connection.stalecheck': determines whether stale connection check is to be used.

Disabling stale connection check may result in a noticeable performance improvement (the check

can cause up to 30 millisecond overhead per request) at the risk of getting an I/O error when

executing a request over a connection that has been closed at the server side. This parameter expects a

value of type https://www.sodocs.net/doc/6916747511.html,ng.Boolean. For performance critical operations the check should be disabled.

If this parameter is not set the stale connection will be performed before each request execution.

'http.connection.max-line-length': determines the maximum line length limit. If set to a positive

value, any HTTP line exceeding this limit will cause an java.io.IOException. A negative or zero

value will effectively disable the check. This parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.Integer.

If this parameter is not set, no limit will be enforced.

'http.connection.max-header-count': determines the maximum HTTP header count allowed.

If set to a positive value, the number of HTTP headers received from the data stream exceeding

this limit will cause an java.io.IOException. A negative or zero value will effectively disable the

check. This parameter expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.Integer. If this parameter is not set, no

limit will be enforced.

'http.connection.max-status-line-garbage': defines the maximum number of ignorable lines

before we expect a HTTP response's status line. With HTTP/1.1 persistent connections, the problem

arises that broken scripts could return a wrong Content-Length (there are more bytes sent than

specified). Unfortunately, in some cases, this cannot be detected after the bad response, but only

before the next one. So HttpClient must be able to skip those surplus lines this way. This parameter

expects a value of type https://www.sodocs.net/doc/6916747511.html,ng.Integer. 0 disallows all garbage/empty lines before the status line.

Use https://www.sodocs.net/doc/6916747511.html,ng.Integer#MAX_VALUE for unlimited number. If this parameter is not set unlimited

number will be assumed.

2.2. Connection persistence

The process of establishing a connection from one host to another is quite complex and involves multiple packet exchanges between two endpoints, which can be quite time consuming. The overhead of connection handshaking can be significant, especially for small HTTP messages. One can achieve

a much higher data throughput if open connections can be re-used to execute multiple requests.

HTTP/1.1 states that HTTP connections can be re-used for multiple requests per default. HTTP/1.0 compliant endpoints can also use similar mechanism to explicitly communicate their preference to keep connection alive and use it for multiple requests. HTTP agents can also keep idle connections alive for a certain period time in case a connection to the same target host may be needed for subsequent requests.

The ability to keep connections alive is usually refered to as connection persistence. HttpClient fully supports connection persistence.

2.3. HTTP connection routing

HttpClient is capable of establishing connections to the target host either directly or via a route that may involve multiple intermediate connections also referred to as hops. HttpClient differentiates connections of a route into plain, tunneled and layered. The use of multiple intermediate proxies to tunnel connections to the target host is referred to as proxy chaining.

Plain routes are established by connecting to the target or the first and only proxy. Tunnelled routes are established by connecting to the first and tunnelling through a chain of proxies to the target. Routes without a proxy cannot be tunnelled. Layered routes are established by layering a protocol over an existing connection. Protocols can only be layered over a tunnel to the target, or over a direct connection without proxies.

2.3.1. Route computation

RouteInfo interface represents information about a definitive route to a target host involving one or more intermediate steps or hops. HttpRoute is a concrete implementation of RouteInfo, which cannot be changed (is immutable). HttpTracker is a mutable RouteInfo implementation used internally by HttpClient to track the remaining hops to the ultimate route target. HttpTracker can be updated after

a successful execution of the next hop towards the route target. HttpRouteDirector is a helper class

that can be used to compute the next step in a route. This class is used internally by HttpClient.

商务英语口译教程Unite1_Unite4课后习题答案

Unit1 P8 1.我们认为你方的格力空调在这里会很畅销，希望很快收到你们的样品。 2．贵方若能报优惠价并保证收到订单后四周内交货，我方将定期订购。 3.如能报到岸价，折扣以及发货日期等详细情况，将不胜感激。 4.随函附上我方最新的产品目录及CIF 纽约报价单。 5.关于贵方9月29日的询价信，我方就如下产品报价，以我方最后确认为准。 6. 此盘5天内不接受就作撤销论。 7. 很遗憾，我们的价格和你方还盘之间差距太大，所以恐怕我方不能接受你方还盘。 8. 考虑到我们长期以来的贸易关系和友好合作，我方建议你方能接受保兑，不可撤销即期信用证。 9. 石油价格将在未来一段时间内继续下降。 10. 我们还想指出我们主要以承兑交单方式结账。 Unit1 P9 1.（我们正打算订购）We are thinking of placing an order for your Flying Pigeon Brand bicycles. We would be very grateful if you could make us an offer for 200 ones with details. 2. （上述询价已于）The above inquiry was forwarded to you on Oct. 10, but we haven’t received your reply yet. Your early offer will be highly appreciated. 3. （我方的冷冻食品）Our frozen foods have been shipped to many countries where they are received favorably. It would be to your advantage to try out a shipment. 4. （很抱歉，贵方）We are sorry to say that the goods required by you are out of stock for the time being. Therefore we are unable to make you an offer at present. 5. （我方于两个月前）We sent you our Quotation No. 44 two months ago, but we haven’t received any news from you. It would be advisable if you could make an early decision on this matter. 6. （所有报盘都以）All quotations, except firm offers, are subject to our final confirmation. Unless otherwise stated or agreed upon, all prices are without any discount. 7.（许多外国电讯）Many foreign telecommunications companies wish to come into the Chinese market such as AT &T, etc. the competition is very keen. I understand some companies are lowering their prices and offering technical assistance and after-sale services. 8.（很高兴我们）I’m glad that we have settled the price. 9. （我们至多只能再减）The best we can do will be a reduction of another 30 pounds. That’ll be definitely rock-bottom. 10. （我们正在仔细研究）We’re now studying your offer carefully, so we hope that you can keep it open till the end of this month. Unit1 P10 1、我们的还盘与国际市场上的价格一致。如果你们接受，我们将说服客户向你们订货。如果你方不能做进一步的让步，我们就没有必要再谈下去了。我们不妨取消整个交易。顺便说一下，在考虑你方的新报价时，请考虑到我们的佣金问题。 2、我们的报价以合理利润为基础，不是漫天要价。你必须考虑到质量问题。这一行的每个人都知道三星产品质量上乘。如果我们不是朋友，我们愿意以这个价格为你们好。 Unit1 P11

人教版高中语文选修《语言文字应用》第一课第3节《四方异声—普通话和方言》教学设计

《四方异声——普通话和方言》教学设计 教学目标 知识目标了解现代汉语的七大方言组成；了解普通话和方言的关系。 能力目标体会各地方言在语音、词汇、语法上与普通话的区别。 情感目标培养对祖国各地语言的认同和热爱。 教学重点了解现代汉语的七大方言组成；了解普通话和方言的关系；通过各地方言的比较，了解方言与普通话的差异。 教学难点了解普通话和方言之间的区别和联系。 教学过程 导——都是什么惹的祸？ 1.笑话三则。 ⑴四川方言笑话： 两个四川人到北京观光旅游，由于对北京的地理环境不熟悉，就在公交车上打开地图研究。 甲：“我们先杀(去)到天安门，然后再杀到毛主席纪念馆，最后杀到中南海……” 乙：“要得嘛，我们就按照你说的路线一路杀过切。” 不幸被同车群众举报，下车后即被扭送至公安机关，交代了若干小时情况后才被放出。 甲乙两人又来到了天安门广场，看着人来人往,两人一时无语…… 甲："你啷个不开腔喃？" 乙："你都不开腔我啷个敢开喃？" 话音刚落，又被广场群众扭送至公安机关。 一周后两人走出了看守所大门，你看看我，我看看你。 甲：“这哈安逸了，包包都遭整空了，哪点去搞点子弹……” 武警冲上来就将两人按倒。 ⑵湖南方言笑话： 某县推广普通话，大会上—— 县长讲完以后，主持人说：“咸菜请香肠酱瓜！”（现在请乡长讲话！）

乡长说：“兔子们，虾米们，猪尾巴！不要酱瓜，咸菜太贵啦！”（同志们，乡民们，注意吧！不要讲话，现在开会啦！） 乡长说：“不要酱瓜，我捡个狗屎给你们舔舔……”（不要讲话，我讲个故事给你们听听………） 乡长说：“兔子们，今天的饭狗吃了，大家都是大王八！”（同志们，今天的饭够吃了，大家都是大碗吧！） ⑶山西方言笑话： 一对新人结婚后第一天清晨，一家人起床洗脸，新娘恭恭敬敬地对婆婆说："婆婆，请您先死(洗)。"说完，新娘又对新郎说："婆婆死了，你死好吗？"停了停又说："婆婆和你都死了，最后我死。"婆婆听后，脸色铁青，一句话也说不出。新娘又说："婆婆，您怎么还不死呢？" 2.小结：都是方言惹的祸！ 思——问方言你为何物？ 1.什么是方言？方言为什么会影响人们交流？ 方言是指同一种语言在不同地域的分支，或者说是一种语言的地域变体。汉语就是一种有许多方言的语言。方言通行于一定地域的民族语言的地域变体，方言没有优劣之分。 2. 什么是普通话？ 普通话是“以北京语音为标准音，以北方话为基础方言，以典范的现代白话文著作为语法规范”的现代汉民族共同语，这是在1955年的全国文字改革会议和现代汉语规范问题学术会议上确定的。 3. 中国有哪些方言？ 根据方言间在语音、词汇、语法上的一些重要差异，现代汉语分成七大方言，即北方方言、吴方言、湘方言、赣方言、客家方言、粤方言、闽方言。 4.普通话也是一种方言吗？它与方言有何关系？ 普通话是汉民族的共同语，也是全中国各民族的通用语。从某种意义上说，普通话也是一种特殊的方言，也就是说，汉语是一个个具体的方言来体现的；但普通话又不同于方言。它是一种最具影响力和模范作用的权威方言。由此可见，作为共同语的普通话也以方言底色

英语口译教程

李天舒 主审：冯伟年 编委李天舒朱益平李艳李淑侠赵晓铃 张春娟张录侠何华李超慧宋美盈 世界图书出版公司2003 年出版定价：15 元 本教材出版后已作为英语系2001 级，辅修班2002 级，专升本2001 级学生口译课教材。 ： 1．题材广泛，内容丰富，实用性强。本教材以我国对外交流与合作及口译工作的实际为出发 点，集口译理论、技巧和实践为一体。内容主要包括口译的基本理论、方法和技巧，涉外工作的礼仪 和程序等，重点是口译工作所涉及的各种话题的英汉互译。这些专题材料主要选自国内外中英文报 刊和有关网站的最新资料。题材广泛，内容丰富、涵盖了我国对外交流中可能涉及到的各种话题，旨 在通过大量的英汉互译实践，使学生掌握口译的基本理论和技巧。 2．英译汉、汉译英并重，双向训练同步进行。口译教学不同于书面翻译教学，可采取英译汉、 汉译英分阶段进行。口头交际是一种双向交际活动；口译通常是在两种语言连续交替转换模式中进 行。因此，口译教学采取英汉互译，双向训练同步进行为好。本教材的总体框架就是根据这一原则设 计和编写的。口译实践是全书的主体部分 本教材分两大部分，十八个单元。第一部分三个单元。第一单元着重介绍口译的基本理论，包括 口译的产生、发展、特点、标准、类型、过程及口译人员的基本素质要求等。第二、三单元集中介绍口译 的一些基本方法和技巧，包括直译法、反译法、意译法、增减译法、口译笔记及各种数字的口译及习语、 引语的口译。另外，第二、三单元在介绍了每一种口译技巧之后都附有相应的英汉互译练习及练习参 考答案。在使用本教材时，教师可根据教材顺序，集中一段时间进行口译理论和技巧教学，着重对 学生进行单项口译技巧训练，使他们通过口译实践尽快掌握口译的基本理论、方法和技巧，闯过口 译中经常遇到的几个难点，为在后面的专题口译训练中能灵活机动、综合运用各种口译技巧，顺利 进行英汉互译打好基础。

部编版三年级下册道德与法治教学设计--请到我的家乡来第一课时

部编版道德与法治三年级下册 7请到我的家乡来第一课时教学设计课题请到我的家乡来第一课时单元第二单元学科道德与法治年级三年级 学习目标1、情感态度与价值观目标：通过了解自己家乡的自然环境，激发热爱家乡的情感。 2、能力目标：培养学生搜集整理资料、合作探究的学习能力。 3、知识目标：认识自己家乡的地理位置、所属的行政区域，了解家乡的自然风光、风景名胜。 重点了解家乡的自然风光、风景名胜，激发热爱家乡的情感。 难点了解家乡的自然风光、风景名胜，激发热爱家乡的情感。 教学过程 教学环节教师活动学生活动设计意图导入新课1、播放视频《桂林山水》 2、人人都把我家乡夸：展示夸赞桂林山水的诗句。 3、一起来朗诵：人人都说家乡好。 4、导入语：谁不说自己的家乡好？谁都说自己的 家乡好！那么，你的家乡在哪里呢？ 思考。视频导入。 讲授新课【我的家乡在哪里】 1、猜一猜：你能根据下面的提示，猜出这几位同 学的家乡在哪里吗？ （1）我家乡的电话区号是010。 （2）我家乡的简称是“苏”。 （3）我的家乡有美丽的漓江。 （4）紫荆花是我家乡的区花。 2、小活动：你能也出一道这样的题目，让大家猜 猜你的家乡在哪里吗？ （1）我家乡的姑娘都被成为“辣妹子”，还有 一首专门写给我们的歌《辣妹子》。 （2）我的家乡被成为天府之国。 （3）我的家乡是以“粤语”为主要语言的省份。（4）我的家乡会用“献哈达”的礼仪来表达敬 意和祝贺。 3、小活动：我的家乡在这里。 （1）你能在地图上找到你家乡所在的省级行政区猜一猜。 猜一猜。 通过猜一猜的活 动，家乡对家乡 基本常识的了 解。

吗？请你找一找，指出来给我们看看吧！ （2）找到后描一描它的轮廓，想象一下它像什么。（3）再试着在地图上找一找你家乡的邻居：毗邻 的省、自治区、直辖市、特别行政区。 4、我的家乡在这里： （1）我的家乡在黑龙江省，我觉得它像一只大白 鹅。在它隔壁的是呼伦贝尔省和吉林省。 （2）我的家乡在内蒙古自治区，我觉得它像一只 奔跑的小狐狸。和它相邻的有黑龙江、吉林、辽宁、河北、山西、陕西、宁夏、甘肃八个省份。 （3）我的家乡在广东省，我觉得它像一只香喷喷 的大鸡腿。和它相邻的有江西、福建、广西、海南、湖南五个省份和澳门、香港两个特别行政区。 5、过渡语：原来同学们的家乡就在这些地方，既 然我们已经知道了地点，那么就让我们一起购买车 票，搭上旅游的巴士，一起去看看吧！ 【我是家乡小导游】 1、师：每个人的家乡都有着独特的自然风光，我 们一起来到你的家乡，你可要当仁不让地当我 们的小导游呀！让我们一次准备准备，带大家 到自己的家乡游玩一番，让更多人了解我们的 家乡吧！ 2、活动前准备： （1）想一想，你要向大家介绍你家乡的哪里风光 景点呢？ （2）请准备好这些旅游景点的照片，了解一下相 关的传说，写一段导游词来为大家介绍吧！ 3、提问：谁先来当家乡的小导游呢？ 4、示例：我当家乡小导游——桂林 （1）桂林游第一站——象鼻山。 （2）桂林游第二站——漓江。找一找、说一 说。 导游前准备。 根据写好的导 游词、展示照 认识家乡的地位 位置，认识家乡 所属的行政区划 以及相邻的行政 区。 通过当小导游的 活动，加深对家 乡的了解和认 识，并增强对家 乡的热爱之情。

商务英语口译教程.doc

商务英语口译教程 下面是整理的商务英语口译教程，希望对大家有帮助。 基本信息 中文名称：商务英语口译教程 作者：李鸿杰 出版社：机械工业出版社 出版时间：2010年02月 ISBN：978*********17 开本：16开 内容简介 《商务英语口译教程》共分4个部分，包括口译理论与技巧、一般商务往来、商务谈判以及英语口译考试介绍;以理论做支撑，围绕商务活动的各个环节展开，同时兼顾口译考试的需要;各个部分相辅相成，互相关联。《商务英语口译教程》可作为高职高专商务英语、国际贸易等专业的英语口译教材及口译考试参考书，也可供从事国际商务工作的人员参考使用。 图书目录 前言 Part 1 Theories and Skills of Interpretation口译理论与技巧1 Unit 1 An Overview of Interpretation口译概述1 Unit 2 Business Interpretation Skills商务口译技巧4 Part 2 General Business Relations一般商务往来20

Unit 1 Meeting at the Airport机场接机20 Unit 2 Accommodation Arrangement住宿安排29 Unit 3 Welcome Dinner欢迎宴会38 Unit 4 People Introduction人员介绍50 Unit 5 Schedule Arrangement日程安排60 Unit 6 Company Profile公司概况69 Unit 7 Product Introduction产品介绍77 Unit 8 On?site Trip现场参观87 Unit 9 Sightseeing观光游览97 Unit 10 Shopping Guide购物指导106 Unit 11 Farewell Party送别宴会114 Unit 12 Seeing the Guest Off送客离别122 Part 3 Business Negotiation商务谈判132 Unit 1 Price，Quantity，Discount and Commission价格，数量，折扣及佣金132 Unit 2 Quality of Product产品质量141 Unit 3 Terms of Payment支付条款148 Unit 4 Time of Delivery交货日期156 Unit 5 Insurance保险163 Unit 6 Agency代理173 Unit 7 Import of Complete Plant成套设备进口184

2019下初中音乐学科知识与教学能力答案及解析

2019下半年全国统考教师资格《初中音乐学科知识与能力》参考答案及解析 一、单项选择题（本大题共30小题，每小题2分，共60分） 1. 答案：G音乐与相关文化 2. 答案：A 3. 答案：B学生聆听阿根廷探戈音乐，尝试敲击典型的探戈节奏 4. 答案：D内心听觉 5. 答案：C在小组中以手鼓拍打节拍 6. 答案：A通过小组合作，学生自主学习歌曲 7. 答案：C学生随音乐哼唱主题并模仿溜冰的动作 8. 答案：C三拍子指挥图示 9.答案：C③ 10.答案: Bo创造 11.答案: Ao《诗经》 12.答案: Ao《白毛女》 13.答案: D《绣红旗》 14.答案: Bo首演由小提琴家吕思清担任独奏 15.答案: A。上下句 16.答案: D苗族芦笙舞 17.答案: Bo琵琶 18.答案: Bo《西游记》 19.答案：C四声部

20.答案：C o 《第六（田园）交响曲》 21.答案： D b《A大调军队波二舞曲》 22.答案： A 。 《波吉与贝丝》 23.答案：Bo单簧管 24.答案：Bo打击乐器 25.答案： D b爱尔兰 26.答案： C o第 4小节 27.答案：Bo螺蛳结顶 28.答案： D b阻碍终止 29.答案： C o第 3小节 30.答案：A ABCABC 二、音乐编创题（本大题共1小题，共10分） 31. 参考答案【缺谱例】 三、音乐作品分析题（本大题共1小题，共15分） 32. 参考答案 1-5 心。tO-13 14-17 1S-2122-25 （2）带再现的单三部曲式。 （3）再现部分是第一段的变化重复，旋律出现在第一段的高八度位置，这样的旋律创作手法 可以使第三乐段与第一乐段相呼应，并在音区上进行对比，既协调又统一，增加了乐曲的表 现力。 四、教学设计题（本大题共1题，共35分） 33. 参考答案（1）教学目标 【情感态度价值观】通过学习作品能够在情感上受到熏陶，感受生活的美好，对爱的表达有更深的感悟。

口译教程参考答案整理版

Lesson 1 美国副总统复旦演讲 韩市长，非常感谢您！谢谢您做介绍时的友好言辞。今天我们很高兴来到这里。我和我夫人为有这次机会再次来到中国访问感到荣幸。感谢贵国对我们的欢迎，特别感谢复旦大学的热情接待。我们为此感到不胜荣幸，谢谢你们！我们此行带来了布什总统和美国人民的良好祝愿。 我知道在座的许多人很快就要从这所优秀的大学毕业。我听说贵校有极为严格的标准，得到复旦大学的学位代表着多年的刻苦攻读和自我约束。我祝贺在座各位学业有成。对各位老师坚持复旦大学99年追求卓越的传统我深表钦佩。 Speech by Wang Guangya at Princeton University Ladies and Gentlemen, Good evening. I am honored to be invited to your seminar tonight. For me, for my colleagues and for many other Chinese, Princeton has long been a familiar name. With a history longer than the country, it has produced many outstanding people, Woodrow Wilson, the 28th US president, Albert Einstein, the great scientist, and T. S. Eliot, the famous poet, to name but a few. As former president Bill Clinton said in 1996 at the celebrations for the 250th anniversary of Princeton,“At every pivotal moment in American history, Princeton, its leadership, faculty and its students have played a crucial role.” ; I am more pleased to learn that all of you have a keen interest in China. Though our two countries are geographically far apart, we have a great deal in common in the everyday life. While many Chinese enjoy Hollywood movies and McDonald’s fast food, many Americans find that their clothes and daily necessities are made in China. I hope that today’s sem inar will help you gain a better understanding of China and its foreign policy, thus deepening further our friendship and cooperation. 新工厂落成典礼上的讲话 各位尊敬的来宾，女士们，先生们：下午好！ 欢迎大家前来参加我们公司在中国的首家新厂房的落成典礼！感谢各位拨冗光临，与我们共同庆祝这一盛大的活动！ 我谨代表公司对今天来参加典礼的各位供应商、客户嘉宾、各位员工和业务伙伴说声“谢谢！” ` 公司管理层深深为我们的新工厂感到骄傲，我们能干的员工感到骄傲，他们发展了工厂的业务，使之达到国际水平。 新厂房标志着公司对中国业务的重视和承诺。 各位供应商，我们希望与你们携手共进，使我们的业务更上一层楼。 各位经销商，我们将继续向你们提供尖端的高质量产品，以协助你们做好客户支持，改善中国和东南亚许许多多人士的生活。 各位邻居和朋友，我们将成为良好的企业公民，与各位同行一起维护在中国开展业务的规范性。 最后，我们承诺给员工们提供一个安全、舒适的工作环境。 再次感谢各位与我们共同庆祝今天的典礼！ Lesson 2

口译教程UNIT 2 第二单元教案

UNIT 2 第二单元教案 来源：口译-学院精品课程作者：Jay J Yang Memoria Technica (II) 口译记忆（二) Unit Objective (单元目标) After reading this unit you should ☆ understand the process of memorization. ☆ master the “Memoria Technica”. Warm-up (准备) 1. Two students are requested to sit at the Interpreting Desk or Booth, acting as interpretors of the class. Their performance is evaluated and graded by instructor. 2.One or Two students are asked to present a piece of news or a weather forecast of the week. Theory of Interpretation II (口译理论二) 口译记忆过程：源语信息编码+信息存储+信息提取+译语信息解码 口译记忆方法：源语复述；总结概括；逻辑整理；影子练习。 Memoria T echnica (记忆法) Listen to the following sentences, and try to catch the key words and details, then repeat as accurately as possible: A. Two sentences repeating:: Sentences from Textbook Unit One as a part of review: 1.20 years ago, almost to the day, President Ronald Reagan spoke at this university and expressed the essence of economic and political freedom. https://www.sodocs.net/doc/6916747511.html,pared to President N ixon’s, or even President reagon’s day, many Chinese citizens are now freer to make their own ways of life ---- to choose carers, to aquire property, and to travel. 3.China’s economic success has also come about through far greater integration into the world economy. In the last decades, your country has

尔雅-语言与文化答案

尔雅-语言与文化答案

本套题正确率15/168=91% 人类起源非洲假说的语言学分析（一）已完成 1 下列关于人类起源非洲假说的内容中正确的是（）。 ?A、能人走出非洲 ?B、南猿人走出非洲 ?C、元谋人走出非洲 ?D、直立人走出非洲 我的答案：D 2 下列哪一项是人类进化的形态之一？（） ?A、山顶洞人 ?B、智人 ?C、北京人 ?D、元谋人 我的答案：B 3 符号活动出现于（）。 ?A、南猿时期 ?B、直立人时期 ?C、晚期智人 ?D、早期智人 我的答案：C 4 人类起源非洲假说是指人类发源于非洲，然后移动到世界各地。（） 我的答案：√

5 某一人群的mtDNA变异越大，它的群体演化历史越短。（） 我的答案：×

人类起源非洲假说的语言学分析（二）已完成 1 非洲智人最早移动到哪一大洲？（） ?A、北美洲 ?B、南美洲 ?C、亚洲 ?D、澳洲 我的答案：C 2 非洲智人什么时候开始走出非洲？（） ?A、20万年前 ?B、13万年前 ?C、15万年前 ?D、10万年前 我的答案：A 3 下列哪一项事物的出现不能标志着智人具有了一定的符号编码能力？（） ?A、图画

?B、雕刻 ?C、文字 ?D、瓷器 我的答案：D 4 智人走出非洲有几条路线？（） ?A、1 ?B、2 ?C、3 ?D、4 我的答案：B 5 直立人是语言人，智人不是语言人。（） 我的答案：× 6 人类起源非洲假说为人类的基因和语言研究提供了重要依据。（） 我的答案：√ 人类起源非洲假说的语言学分析（三）已完成

1 脑容量与语言的关系是（）。 ?A、正相关 ?B、负相关 ?C、没关系 ?D、不确定 我的答案：A 2 方言的形成有几种方式？（） ?A、3 ?B、2 ?C、4 ?D、5 我的答案：B 3 （）对我国南方汉语方言的形成起了不可估量的作用。 ?A、语言接触 ?B、语言融合

仲伟合：英语口译教程

第二部分练习篇 Exercise One Listen to the following texts and then reproduce in the same language at the end of each segment: Text 1.1 Mr Governor, Ladies and Gentlemen, It is my great pleasure to be invited to attend the Guangdong Governor?s International A dvisory Council Meeting.// I would like to take this opportunity to highlight our report to the Governor and share with you our view on the role of telecommunications and information infrastructure (ICT) in the economic development.// International experience suggests that Information and communication technology (ICT) infrastructure and services can have a substantial impact on the competitiveness of firms, nations, and regions. The most important impact of ICT does not come from manufacturing ICT goods, but from investing in and using ICT infrastructure and services.// According to the ITU, global telecommunications services sales reached US$ 1.1 trillion in 2002, more than three times the value of telecommunications equipment sales of US$335 billion. The value created by use of telecommunications services is estimated to be far higher than the total services revenue. Thus investment in ICT infrastructure creates value many times that of the investment itself. // Firm level studies show that ICT investments help firms gain competitiveness through improved efficiency, reduced inventories, better designs, and faster rates of innovation. ICT allows firms to increase the efficiency of their business processes by decreasing procurement and transaction costs, improving accounting and control, enhancing management systems, and streamlining their supply chains.// Several studies also indicate that ICT is a key driver of productivity and growth. There are several distinctive features of ICT that make them particularly important to national and regional economies, which include the pervasive and cross-cutting nature of ICT, the low or declining marginal costs of using the technologies, the ability to foster efficiency gains through streamlining supply chains, the facilitation of the creation of entirely new business models and industries, and the global nature of ICT.// All of these characteristics imply that ICT can have an important impact on competitiveness and economic development.// Text 1.2 主席先生： 我很高兴参加2001’国际投资论坛。我愿意借此机会，向大家介绍一下中国加入WTO 谈判和对外开放的有关情况。// 15 年“复关”和加入WTO 的马拉松谈判到今天应该说已经到了最后阶段。继1999 年11 月中美达成双边协议，2000 年5 月中欧达成双边协议后，中国加入WTO 进程加快，截止2000 年9 月，除墨西哥外，双边谈判已经基本结束。墨方曾多次表示即使不能达成协议，也不会影响中国加入WTO 的进程。//

办公软件教程(含wordexcelppt)-从零基础学起

办公软件教程-从零基础学起 Office XP主要包括：字处理软件Word、Excel、PowerPoint等应用程序。它们具有统一的界面、相似的常用工具栏及大同小异的操作方法，只是各自的侧重点有所不同。 Word是文字处理软件。它集成文字处理、表格处理和图形处理于一体，汇集了对各种对象的处理工具，使图片、图表、表格、艺术字等的处理得心应手。 Excel是以表格化数据处理为基础的集成化处理软件。它不但能实现电子表格数据处理，也具有数据库管理、统计图表自动生成等功能。 PowerPoint是创作电子演示文稿的软件。利用它可以方便地制作出集文字、图形、图像、声音、视频和动画于一体的多媒体演示文稿。 一、Word特点

1．对文档提供了多种查看方法； 如：普通视图、页面视图、大纲视图、Web版式视图、文档结构图、全屏显示、Web页预览、打印预览等。 2．具有专业级的表格处理功能； 3．使用方便的多栏彩色图文混排、艺术字处理； 4．具有功能很强的数学公式编辑器； 5．具有多种类型文件的转换功能。 二、窗口介绍 菜单栏、常用工具栏、格式工具栏、正文编辑区、状态栏、标尺、滚动条等。 注：工具栏的显示与隐藏（视图→工具栏→各种工具栏。） 三、页面设置：“文件”→“页面设置”。 1．纸张的大小（常用的纸张：A3、8K、B4、A4、16K、B5。） 2．设置页边距：调整正文到纸张边界[2] []大2小。 四、文档编辑 1．建立文档（Ctrl + N） （1）录入文字，录入时不要排版，每（）1一段敲一次回车，每段前空两个汉字位置。（2）特殊符号录入：“插入”→“符号”或用动态键盘。 （3）显示/隐藏文档中的非打印符号。 2．保存文档 （1）保存（Ctrl + S） （2）另存为 3．打开和关闭文件（打开：Ctrl + O） 4．文档选择基本方法 （1）拖动选择

《口译》课程教学大纲及教学的计划.doc

《口译》课程教学大纲及教学计划 一.课程设置的目的与目标 2000年4月《高等学校英语专业英语教学大纲》经教育部高教司批准下发执行。新《大纲》规定高等院校英语专业的培养目标为：“具有扎实的英语语言基础和广博的文化知识并能熟练地运用英语在外事、教育、经贸、文化、科技、军事等部门从事翻译、教学、管理、研究等工作的复合型英语人才；其规格为：“扎实的基本功、宽广的知识面、一定的相关专业知识、较强的能力和较高的素质”。 口译是一门语言技能与专业知识相结合的课程。本课程以口、笔译理论和其他相关学科理论作指导，通过讲授口译基本技巧以及各种交际环境中语言的正确表达方式、全方位地对学生进行口译技巧和逻辑推理能力训练，并结合课外口译实践，拓宽学生知识面，培养学生跨文化交际能力、口译相关技巧的综合运用能力、认知、推理能力、独立工作能力、解决问题的能力以及相应的心理素质。 二.口译课开设年级及课时安排 第六、第七学期，周学时2。 三.课程教学对象 英语专业大三学生 四.口译课教学要求 为了更好地因材施教，根据我系生源、学生专业方向以及西部地区口译市场现状，我系口译教学大纲在教学要求上分为三个层次。 通过讲授口译基本理论、口译背景知识以及对学生进行口译基本技巧的训练，结合口译实践，使学生掌握口译的基本理论和专题连续传译的技能，初步学会口译记忆方法、口译笔记、口头概述、公众演讲等基本技巧和口译基本策略，培养学生的话语分析能力，提高学生的逻辑思维能力、语言组织

能力和双语表达能力，学生能担任一般外事活动的交替传译。注意培养学生 关心时事的信息意识，积累知识，掌握文献检索、资料查询的基本方法，具 有初步研究能力和实际工作能力，提高各项交际技能综合运用的能力，提高 学生的综合人文素质。 五.口译课教学原则 我系口译教学以国家教委颁布的《高等学校英语专业英语教学大纲》中 教学原则为指导原则，结合我系生源、学生专业方向以及西部地区翻译市场 现状，实行立体型、交叉式的口译教学模式。口译教学的重点放在培养学生 的跨文化交际能力、口译相关技巧的综合运用能力、认知、推理能力、独立 工作能力、解决问题的能力以及相应的心理素质。 六.口译课教学方法与教学手段 从“口译基本功”训练、“口译语言技能”训练、“口译对话翻译能力”训练、“口译实战”训练，一直到“口译专业技能训练”，“4+1”翻译班的“层次思维训练法”，以层次递进的方式，系统、有序和全方位地引导学员掌握口译的技能和能力；并通过交传和同传并重、普通班和翻班齐上的套餐形式，将学生从 听说的专业技能顺利地过渡到口译的专业技能的培训上，在一定程度上实现 相关专业与外语专业之间的复合、交融与渗透，使学生从语言的单一性向知 识的多元化、宽厚型方向转化。 七.口译教学参考文献 1、理论部分 1.《口译技巧—思维科学与口译推理教学法》，刘和平，北京：中国对外翻 译公司，2001年。 2.《口译理论与实践》，刘和平，中国对外翻译出版公司，2005年5月。 3.《口译理论概述》，鲍刚，北京：旅游教育出版社，1998。 4.《口译须知》<瑞士> 让·艾赫贝尔著，孙慧双译，北京：外语教学与研 究出版社1982年5月第一版。 5.《口译理论-实践与教学》<法> 达尼卡·塞莱斯科维奇、玛丽亚娜·勒代 雷著，汪家荣等译，北京：旅游教育出版社1990年。

最新广东省汕头市高三第二次教学质量检测汕头二模文综试题

广东省汕头市2013年高三第二次教学质量检测汕头二模文综 试题

广东省汕头市2013年高三第二次教学质量检测(汕头二模）文综试题 政治试题及部分详细解析 一、单项选择题 24、在一般条件下“物丰价廉”与“物美价廉”分别意味着 A供求影响价格使用价值决定价格 B 生产者获利减少消费者需求增加 C生产力提高企业经营成功 D市场调节有其弊端宏观调控有其优势 解析价值决定价格A 排除“物丰价廉”即丰产不丰收生产者获利会减少。“物美价 廉”是消费者追求的目标故消费者需求增加选B。“物丰价廉”与生产力提高没有必然 关系企业经营成功意味着其生产的产品无论在产品质量还是价格方便都具有竞争优 势故C不选。市场调节的弊端有自发性、盲目性、滞后性其中的自发性与滞后性与“物 仅供学习与交流，如有侵权请联系网站删除谢谢2

丰价廉”没有必然关系。宏观调控的主要目标之一是稳定物价而“物美价廉”与宏观调控 没有必然的关系。故D 与题意不符。 25、假定其他条件不变图4中的曲线表现的变动 关系必须是 A、X表示社会劳动生产率Y表示商品价 值量 B、X表示恩格尔系数Y表示家庭生活水 平 C、X表示人民币汇率Y 表示外汇汇率 D 、X表示居民收入水平Y表示居民消费水平 解析A中社会劳动生率与商品价值量成反比。B中恩格尔系数与家 庭生活水平成反比C中人民币汇率与外汇汇率也成反比。D中居民收 入水平与居民消费水平成正比图象为正比例函数故选D。 26西方经济学家曼昆认为政府不是喂养于天国的母牛经济环境不好时政府要出手救 市。下列属于政府救市的措施有 ①降低银行利率②减轻企业税收负担③减少国债发行④减少财政支出 A、①② B、③④ C 、①③ D ②③ 解析题干中的条件是“经济环境不好时”政府应实行扩张性的货币政策与扩张性的财政 仅供学习与交流，如有侵权请联系网站删除谢谢3

大学英语口译教程答案第2单元

Unit 2 Passage 1 英国女王2009 圣诞致词 过去每年似乎都各具特点。一些年份让我们心满意足，一些年份则最好忘却。2009 年对很多人来说都是艰难的一年，尤其是那些深受经济衰退之苦的人们。 我相信，我们所有人都受到阿富汗战事影响，为英军士兵伤亡感到悲伤。我们向这些 士兵的家人和朋友表示慰问，他们面对巨大个人损失表现得无比高尚。 但我们应该为我们的士兵与盟友一道作出的积极贡献而感到骄傲。英国和包括加拿 大、澳大利亚、新西兰和新加坡在内的英联邦国家眼下共有超过1.3 万名士兵在阿富汗服役。我们对这些年轻士兵以及先前在阿富汗服役过的士兵表示深深感激。 今年是英联邦成立60 周年，今天其成员国25 岁以下人口超过10 亿，为它保持长 久的强大和实力提供了力量源泉。 最近我刚刚参加了在特立尼达和多巴哥举行的英联邦政府首脑会议，听到联邦对年轻 人是多么重要。新的通讯技术使他们能够接触到更广阔的世界，分享他们的经验和观点。对于许多人来说，英联邦的实际援助与网络可以提供技能，给予意见和鼓励进取。 令人鼓舞的是，我了解到一些年轻人正在做着一些事情，他们面对挑战，富于创造力 和创新精神。 对关系到我们所有人的问题保持讨论很重要，它让我们的大家庭产生更大的价值。在 英联邦成立以来的大部分时间里，我都同它联系紧密。 我珍视同各国领袖、人民之间在个人和生活上的紧密联系，这不单是象征意义上的， 也能促进我们的团结。 英联邦并非只是一个具有某种使命的组织，更是一个让各国人民合作、解决实际困难 的平台。在涉及我们生活的许多方面，不论是体育、环境、商业或文化，英联邦国家之间的联系生动活泼而且丰富多彩。在很多方面这展现未来的前景。随着不断的支持和贡献，我相信多元化的英联邦国家之间能加强超越政治、宗教、种族和经济环境的凝聚力。 众所周知，圣诞节是欢庆与家人团聚的时候，但我们也可以借这个时机反思那些国内 外不幸者面临的困境。 基督徒接受的教义是要爱他们的邻居，有同情心，乐于慈善和志愿工作，以减轻贫困 和弱势者的负担。 我们自己会面临一连串的困难和挑战，这些困难和挑战会令我们感到困惑，但我们绝 不能停下脚步，而应该继续努力，为自己和他人创造更美好的未来。 不论你们现时身在何处，我都祝愿你们圣诞快乐！ 13 Passage 2 美国第一夫人米歇尔·奥巴马在英国伦敦伊斯灵顿伊丽莎白·安德森女校的演讲（节选）这是我的第一次出访，作为第一夫人的第一次外事出访。你们能相信吗？虽然这不是 我第一次来英国，但我得说很高兴我的首次官方访问是来英国。美国和英国之间的特殊关系，不只是基于政府间的关系，还基于我们有共同的语言和价值观。看见你们大家就使我想到这一点。在访问期间我特别荣幸地会见了英国一些最出色的女性，她们在为你们所有女孩子铺路。 我也很荣幸见到你们这些英国和世界未来的领导者，尽管我们的生活背景好像相差很 远，我是作为美国第一夫人站在这里，而你们还正在上学。 但我想让你们了解我们其实有很多共同之处。因为在我生命历程中没有任何东西曾经 预示我会作为美利坚合众国的第一位非洲裔第一夫人站在这里。我的资历里没有什么东西