A Cross-Layer Approach to Performance Monitoring
of Web Services
Nicolas Repp,Rainer Berbner,Oliver Heckmann,and Ralf Steinmetz
Technische Universit¨a t Darmstadt
Multimedia Communications Lab(KOM)
Merckstrasse25,64283Darmstadt,Germany
repp@kom.tu-darmstadt.de
Abstract.An increasing amount of applications are currently built as Web Ser-
vice compositions based on the TCP/IP+HTTP protocol stack.In case of any
deviations from desired runtime-behavior,problematic Web Services have to be
substituted and their execution plans have to be updated accordingly.One chal-
lenge is to detect deviations as early as possible allowing timely adaption of exe-
cution plans.We advocate a cross-layer approach to detect bad performance and
service interruptions much earlier than by waiting for their propagation through
the full protocol stack.
This position paper describes an approach to gain detailed real-time information
about Web Service behavior and performance based on a cross-layer analysis of
the TCP/IP+HTTP protocols.In this paper we focus especially on TCP.The re-
sults are used to make decisions supporting service selection and replanning in
service-oriented computing scenarios.Furthermore,generic architectural compo-
nents are proposed implementing the functionality needed which can be used in
different web-based scenarios.
1Introduction
Almost every Internet user has encountered problems while using services in the Inter-net,e.g.,browsing the World-Wide Web or using Email.Long to in?nite response times due to congestion or connection outage,non-resolvable URLs,or simple?le-not-found errors are some of the most common ones.Human users tend to be?exible in case of any service”misbehavior”.Users wait and check back later or even select a different service if the originally requested service is not available.In contrast,computer systems as service consumers are not as?exible.Appropriate strategies to handle those runtime events have to be implemented during design time of the computer system.
Services are the key building block of service-oriented computing.A service is a self-describing encapsulation of business functionality(with varying granularity)ac-cording to[1].Following the service-oriented computing paradigm,applications can be assembled out of several independent,distributed and loosely-coupled services[2]. Those services can be provided even by third parties.One option to implement services from a technical perspective is the use of Web Services.Web Services are based on dif-ferent XML-based languages for data exchange and interface description,e.g.,SOAP and the Web Service Description Language(WSDL).For the transport of data and the
Fig.1.Modi?ed W3C Web Services Architecture Stack[3]
Web Service invocation mainly the Transmission Control Protocol(TCP)/Internet Pro-tocol(IP)suite(e.g.,RFC793,[4],or[5])as well as the Hypertext Transfer Protocol (HTTP-e.g.,RFC2616or[6])are used.Figure1shows the W3C Web Services Archi-tecture Stack enhanced by alternative Web Service technologies and the communication protocols used.It will be the basis for our further considerations.
In order to build applications from different existing Web Services the following generic phases are needed[7]:First,suitable Web Services have to be selected accord-ing to the functional and non-functional requirements of the application.Second,the selected Web Services have to be composed to an execution plan.Hereto,a composition can be described,e.g.,on basis of the Business Process Execution Language(BPEL) [8].In the next step the execution plan can be processed.During the execution phase it is possible that parts of the composition do not act as expected with regard to the non-functional requirements.Reasons for misbehavior of Web Services are manyfold, e.g.,server errors while processing a request,network congestion or network outages. Therefore,it is necessary to select alternative Web Services and to replan the Web Ser-vice execution[9].Replanning is always a trade-off between the costs of creating new plans to ful?ll the overall non-functional requirements and the costs of breaking the requirements[10].Timely action is required to reduce the delay in the execution of an application due to replanning and substitution of Web Services.Hence,we propose a proactive approach initiating countermeasures as soon as there is evidence that a de-viation might occur in the near future with a certain probability p.To start replanning before the deviation happens allows replanning to be carried out in parallel to the ser-vice execution itself.The results of replanning have to be discarded with probability 1?p as the alternative plans are not needed.
Furthermore,current approaches often lack detailed information about the status of a Web Service due to the information hiding implemented in the layer model of
the TCP/IP+HTTP protocol stack underlying Web Services.For this,we advocate a cross-layer approach to detect bad performance and service interruptions.Cross-layer analysis allows decisions based on deeper knowledge of the current situation as well as decisions made much earlier than by waiting for information propagating through the full protocol stack.
The rest of this position paper is structured as follows.In the next section we de-scribe Quality-of-Service(QoS)and its meaning for Web Services.We especially fo-cus on performance as a part of Web Service QoS.Afterwards,the relation between TCP/IP+HTTP and Web Service performance is discussed.Our cross-layer approach to performance monitoring an performance anomaly detection of Web Services is intro-duced thereafter.The paper closes with a conclusion and an outlook on future work.
2Quality-of-Service and Performance of Web Services
In this section we discuss QoS with regard to Web Services and Web Service composi-tions with a focus on Web Service performance.
2.1Quality-of-Service with regard to Web Services
Similar to QoS requirements in traditional networks,there is a need to describe and manage QoS of Web Services and Web Service compositions.Generally,QoS de?nes non-functional requirements on services independent from the layer they are related to. QoS can be divided into measurable and non-measurable parameters.The most com-mon measurable parameters are performance-related,e.g.,throughput,response time, and latency.Additionally,parameters like availability,error-rate,as well as various non-measurable parameters like reputation and security are of importance for Web Services [10][11].The meaning of QoS requirements can differ between service providers and service requesters in a service-oriented computing environment[11].From a service providers’perspective,providing enough capacity with the quality needed to ful?ll Service Level Agreements(SLA)with different customers is a core issue.Service re-questers are more focused on managing bundles of Web Services from different ven-dors in order to implement their business needs.Therefore,management of QoS re-quirements is done on aggregations of Web Services,to a lesser extend on single Web Services.
There is a variety of other de?nitions of Web Service QoS.A more extensive ap-proach identi?es the following requirements[12]:performance,reliability,scalability, capacity,robustness,exception handling,accuracy,integrity,accessibility,availability, interoperability,security,and network-related QoS requirements.Especially the last re-quirement is of further interest.As many requirements of Web Service QoS are directly related to the underlying network and its QoS,implementations of network QoS mech-anisms,e.g.,Differentiated Services(DiffServ)or the Resource Reservation Protocol (RSVP),are also covered by the de?nition as well.
2.2Performance of Web Services
Performance of Web Services is not a singular concept.Rather,it consists of several concepts which themselves are connected to different metrics and parameters.Again, there are several de?nitions of Web Service performance.We will use the de?nition provided by the Web Services Architecture Working Group of the W3C as a founda-tion for our own de?ntion.According to the W3C,performance is de?ned in terms of throughput,reponse time,latency,execution time,and transaction time[12].Both execution time and latency are sub-concepts of the W3Cs de?nition of response time. Transaction time describes the time needed to process a complete transaction,i.e.,an interaction consisting of several requests and responses belonging together.
For this paper,we de?ne performance in terms of throughput and response time. Response time is the time needed to process a query,from sending the request until receiving the response[13].Response time can be further divided into task processing time,network processing time,i.e.,time consumed while traversing the protocol stacks of source,destination,and intermediate systems,as well as network transport time itself. In case of an error during the processing of a request or a response,the response time measures the time from a request to the noti?cation of an error.We de?ne response time as follows:
t response(ws)=t task(ws)+t stack(ws)+t transport(ws)
A large fraction of a web service’s response time is determined by the processing time for requests and their respective messages in both intermediate systems and end-points. For the measurement of the response time,the encapsulation of data into XML mes-sages and vice versa,compression and decompression of data,as well as encryption and decryption of messages also have to be taken into account.Furthermore,time for con-nection setup,for the negotiation of the connections parameters as well as the amount of time used for authentication are part of the response time as well.
Throughput,measured in connections,requests or packets per second,describes the capability of a Web Service provider to process concurrent Web Service requests.De-pending on the layer,different types of connections can be the basis for measurements, e.g.TCP connections,HTTP connections,or even SOAP interactions.We de?ne the throughput of a Web Services as:
throughput(ws)=#requests(ws)
3A Cross-layer Approach to Performance Monitoring and Anomaly Detection
In this section we describe an approach for performance monitoring and performance anomaly detection based on packet capturing and the application of simple heuristics. Therefore,we analyze IP,TCP,and HTTP data.The analysis of SOAP is not in scope of this paper,as we want to stay independent of a certain Web Service technology.Our approach can be applied to various alternative Web Service technologies as well,e.g., XML-Remote Procedure Call(XML-RPC)or Representational State Transfer(REST). Nevertheless,in our examples we use SOAP as it is the most common Web Service technology in use.
3.1Protocol Parameters for Performance Monitoring
Consider the simple Web Service invocation of a single Web Service as depicted in Figure2.A service requester generates a SOAP request and sends the message using HTTP to the service provider for further processing.The message has to pass several in-termediate systems on its way between the interaction’s endpoints.The SOAP response message is again transported using HTTP.
Service Service
Fig.2.Simple Web Service interaction
During data transfer several problems can occur,which all have an impact on Web Service execution.Beginning with the network layer,we may face routing problems, e.g.,hosts which are not reachable,congestion in Internet routers as well as traf?c bursts.Additionally,on transport layer there are also potential pitfalls like the retrans-mission of packets due to packet loss or connection setup problems generating delays. Finally,there are also some potential problems on application layer with regard to Web Services for example in form of resources,which are not existing or not accessable for HTTP or problems in processing of SOAP messages due to incomplete or non-valid XML data.
Although,many of the above problems are solved in modern protocol stack imple-mentations,we can use the knowledge about them to de?ne measurement points for performance monitoring.Depending on the problems in scope different protocol pa-rameters have to be used.Table1gives an overview of measurement points on different
protocol layers.We will use the transport layer parameters as an example to derive metrics and heuristics for performance anomaly detection in the following section.
Protocol
ICMP messages
Size of advertising window
Roundtrip time(RTT)
Sequence numbers in use
Flags used in packets
Information about timers
Header information
Table1.Measuring points per protocol layer
3.2Metrics and Heuristics for Performance Anomaly Detection
As noted in Section2.1we can differentiate between the requirements of service re-questers and service providers.To visualize our concepts we will focus on the service requester’s perspective in this position paper.Before basic heuristics are proposed we present metrics based on the parameters presented in Table1,which will be the founda-tion of our heuristics.We propose several metrics based on parameters of the transport layer protocol:
–M1-Average throughput in bytes per second(BPS).
–M2-Throughput based on a moving average over window with size n seconds in BPS.
–M3-Throughput based on exponential smoothing(?rst degree)withαvarying in BPS.
–M4-Roundtrip time based on a moving average over window with size n segments in seconds per segment.
–M5-Number of gaps in sequence numbers based on a moving average over window with size n seconds in number of gaps per second.
The aggregation of single metrics in combination with the usage of appropriate thresholds allows us to build heuristics in order to detect anomalies with performance impact.The following two simple heuristics show the idea how to design heuristics based on the metrics discussed.Both were derived from experimentations in our Web Service test environment.
–H1Requester:M1(or M2,M3)in aggregation with M4,i.e.,throughput combined with RTT.
–H2Requester:M4in aggregation with M5,i.e.,RTT combined with the amount of gaps in TCP sequence numbers.
Singular metrics are in some cases not suf?cient for robust monitoring,e.g.,M5without any information about RTT does not offer useful information.
In addition to those transport layer based heuristics,further parameters from other protocol layers and the respective metrics can be combined in order to create different cross-layer heuristics.Nevertheless,it is important that metrics and the related heuristics have to be calculated in an ef?cient way in order to keep additional processing times of our approach low.
3.3Exemplary Evaluation of Our Approach
To show the feasibility of our approach we set up an experiment.The test environment consists of a1.4GHz Centrino with1.256GByte RAM running Windows XP as ser-vice requester and a1.42GHz G4with1GByte RAM running Mac OS X as service provider.Apache Tomcat5.5.17is used as an application server.Both systems use Java 1.5and Axis1.4as SOAP implementation.They are connected by100MBit/s ethernet. For packet capturing windump v3.9.3is used.
First,we measure the response time of a Web Service in our test environment.As payload we use SOAP messages of variable size.Table2shows the results of measuring 20individual runs both with and without network outage for a payload of20MByte,a test scenario,which was already implemented in our test environment.Similar results can be observed with a payload https://www.doczj.com/doc/031037936.html,work outages are equally distributed t response(ws)[ms]maximum
8,7438,891
601,204604,186
Table2.SOAP response times
in the interval[0;max(t response(ws)w/o outage)].A network outage is modelled as a permanent100%packet loss,i.e.,without a restart of the connection.Other scenarios, e.g.,varying or temporary packet loss,are not in focus of this position paper.As Table 2shows,the response time of our Web Service varies between8.9seconds(without outage)and10.07minutes(with outage)for a20MByte payload.
rtt[ms]maximum
0.220.31
Table3.Roundtrip times
In a next step,we apply H1Requester on our sample with network outages.Espe-cially the roundtrip time extracted from TCP packets can be used as trend estimate for the overall response time in our scenario.Table3shows the average roundtrip times of https://www.doczj.com/doc/031037936.html,ing a moving average of the roundtrip times measured as a benchmark
for the roundtrip time of the packet in transfer,a warning to the replanning system can be sent,e.g.,if the estimated time(or a multiple)is exceeded twice or more in a row. Unfortunately,throughput was not as good as the RTT as an indicator for performance anomalies in the given scenario.
3.4Identi?cation of Required Architectural Components
In order to implement our ideas several architectural components are needed.The key building blocks are depicted in Figure3.
Fig.3.Proposed architectural components
The upper part of Figure3describes existing generic components used for planning and executing of Web Service compositions.The Interface allows deployment of work-?ows and con?guration,the(Re-)Planning Component generates and adapts execution plans,which are thereafter executed by an Orchestration Engine.We propose the use of our Web Service Quality-of-Service Architectural Extension(WSQoSX)as imple-mentation means for the functionality needed.WSQoSX already supports planning and replanning of compositions[7][10].
The lower part of the?gure describes the two core components of our approach in addition to the protocol stack.This enhanced architectural blueprint is named Web Service-Service Monitoring Extension(WS-SMX).The Monitor speci?es a compo-nent capable of eavesdropping of the network traf?c between service requester and provider.It also implements pre-?ltering of the data passing by reducing it to the pro-tocol data of interest.Its data is passed to a Detector component,which is responsible
for the data analysis and therefore the performance anomaly detection.The Detector component will implement the heuristics discussed in Section3.2.The Orchestration Engine initializes the Detector,which itself prepares the Monitor.The Detector analy-ses the data received by the Monitor and triggers the(Re-)Planning Component in case of any critical?ndings.Additionally,the Detector component can be con?gured using the Interface.Both Monitor and Detector are implemented in a?rst version in our test environment based on Java1.5in combination with libpcap for packet capturing.
4Related Work
As our approach is based on research of various domains this section gives an overview of related work in those domains.Gschwind et al.[14]describe WebMon,a perfor-mance analysis system with focus on Web transactions,i.e.transactions between a Web browser and a Web server.Monitoring is done on basis of HTTP.Web Services as re-mote method invocations as well as a further processing of the results of the analysis are not in scope of their paper.Similar mechanisms as the ones proposed by us are im-plemented in the commercial software package VitalSuite by Lucent,which is used for capacity planning and QoS management in large networks.VitalSuite can also analyze different protocol layers simultaneously.In contrast to the system we propose,Vital-Suite’s focus is on reporting for end-users instead of automated management.A more detailed view on performance management of Web Services is discussed by Schmi-etendorf et al.[15].The Web Services Trust Center(WSTC)allows Web Services to be registered at and measured by an independent third party for SLA management.WSTC enables the monitoring of performance and availability of Web Services,but not under real-time requirements.
The management of Web Service compositions,their orchestration as well as their optimization and planning is emphasized in various papers,partly mentioned in the introduction.Of further interest in that domain is the Web Service Manager(WSM) introduced by Casati et al.[16]focusing on the business perspective of Web Service management,e.g.,detecting and measuring SLA violations.
Fundamental work in the area of packet capturing,its justi?cation and optimization was carried out e.g.,by Feldmann[17]and Mao et al.[18].Both do not focus on poten-tial areas of application for packet capturing but on measurement itself.Feldmann uses cross-layer capturing and analysis of TCP and HTTP for later Web performance studies. Mao et al.describe both drawbacks and advantages of performance analysis of Web ap-plications based on packet capturing mechanisms.Furthermore,a reliable and ef?cient approach for monitoring in distributed systems based on dispatching is discussed.
The idea of anomaly detection to predict certain critical situations is already used, e.g.,in the area of network security,especially in network intrusion detection.Mainiko-poulos et al.describe the use of statistical methods applied to network usage traces for anomaly detection,e.g.,an attack on a networked system[19].Another area of appli-cation is discussed by Yuan et al.[20].They propose a system for automated problem diagnosis in applications based on system event traces.The correlation of current traces and patterns of well known problems allows an automatic identi?cation of problem
sources and prediction of possible system errors.Furthermore,the authors use statisti-cal learning and classifying methods to dynamically adapt and improve their system. 5Conclusion and Future Work
In this position paper we show that it can be bene?cial to use information gathered on different protocol layers for decision support.We present an approach and several architectural components,which use hidden,low layer technical information for proac-tive replanning of Web Service compositions.As this is a position paper there are still some open issues we are researching.We are currently testing machine learning algo-rithms for anomaly detection.Furthermore,we are working on enhancements of ex-isting optimization models for Web Service compositions to support replanning[10]. Additionally,we will test our approach from a service requester’s perspective in real world scenarios,using Web Services available to the public,e.g.,from Amazon or via Xmethods.
Using our approach for proactive replanning is not limited to SOAP Web Services. As we are collecting our data on lower layers,the type of Web Service can be ex-changed,e.g.,REST and XML-RPC based Web Services can also be supported.But we are not even limited to Web Services as an area of application.The approach can be of bene?t,e.g.,to enhance Web browsers to detect network problems in a faster way. Acknowledgments
This work is supported in part by E-Finance Lab e.V.,Frankfurt am Main. References
1.Papazoglou,M.P.:Service-oriented computing:Concepts,characteristics and directions.In:
Proceedings of the Fourth International Conference on Web Information Systems Engineer-ing(WISE03).(December2003)3–12
2.Bichler,M.,Lin,K.J.:Service-oriented computing.IEEE Computer39(3)(March2006)
99–101
3.Booth,D.,Haas,H.,McCabe,F.,Newcomer,E.,Champion,M.,Ferris,C.,Orchard,D.:Web
services architecture(2004.https://www.doczj.com/doc/031037936.html,/TR/ws-arch/,accessed:2006/07/02)
4.Stevens,W.R.:TCP/IP illustrated(vol.1):the protocols.Addison-Wesley Longman Pub-
lishing Co.,Inc.,Boston,MA,USA(1994)
5.Tanenbaum,A.S.:Computer Networks,Fourth Edition.Prentice Hall,Indianapolis,Indiana,
USA(August2002)
6.Mogul,J.C.:Clarifying the fundamentals of http.In:WWW’02:Proceedings of the11th
international conference on World Wide Web.(May2002)25–36
7.Berbner,R.,Grollius,T.,Repp,N.,Heckmann,O.,Ortner,E.,Steinmetz,R.:An approach
for the management of service-oriented architecture(soa)based application systems.In: Proceedings of the Workshop Enterprise Modelling and Information Systems Architectures (EMISA2005).(October2005)208–221
8.Curbera,F.,Khalaf,R.,Mukhi,N.,Tai,S.,Weerawarana,S.:The next step in web services.
Commun.ACM46(10)(2003)29–34
9.Canfora,G.,Penta,M.D.,Esposito,R.,Villani,M.L.:Qos-aware replanning of compos-
ite web services.In:Proceedings of the IEEE International Conference on Web Services (ICWS’05).(July2005)121–129
10.Berbner,R.,Spahn,M.,Repp,N.,Heckmann,O.,Steinmetz,R.:An approach for replanning
of web service work?ows.In:Proceedings of the12th Americas Conference on Information Systems(AMCIS’06).(August2006)
11.Menasc′e,D.A.:Qos issues in web services.IEEE Internet Computing6(6)(2002)72–75
12.Lee,K.C.,Jeon,J.H.,Lee,W.S.,Jeong,S.H.,Park,S.W.:Qos for web services:Require-
ments and possible approaches(2003.http://www.w3c.or.kr/kr-of?ce/TR/2003/ws-qos/,ac-cessed:2006/07/03)
13.Jain,R.:The art of computer systems performance analysis:techniques for experimental
design,measurement,simulation,and modeling.John Wiley&Sons,Inc.,New York,NY, USA(1991)
14.Gschwind,T.,Eshghi,K.,Garg,P.K.,Wurster,K.:Webmon:A performance pro?ler for web
transactions.In:Proc.of the4th IEEE Int’l Workshop on Advanced Issues of E-Commerce and Web-Based Information Systems-WECWIS2002.(June2002)171–176
15.Schmietendorf,A.,Dumke,R.,Stojanov,S.:Performance aspects in web service-based
integration solutions.In:Proc.of the21st UK Performance Engineering Workshop-UKPEW2005.(July2005)137–152
16.Casati,F.,Shan,E.,Dayal,U.,Shan,M.C.:Business-oriented management of web services.
Commun.ACM46(10)(2003)55–60
17.Feldmann,A.:Blt:Bi-layer tracing of http and tcp/https://www.doczj.com/doc/031037936.html,works33(1-6)(2000)
321–335
18.Mao,Y.,Chen,K.,Wang,D.,Zheng,W.:Cluster-based online monitoring system of web
traf?c.In:WIDM’01:Proceedings of the3rd international workshop on Web information and data management.(November2001)47–53
19.Manikopoulos,C.,Papavassiliou,S.:Network intrusion and fault detection:a statistical
anomaly approach.IEEE Communications Magazine40(10)(October2002)76–82
20.Yuan,C.,Lao,N.,Wen,J.R.,Li,J.,Zhang,Z.,Wang,Y.M.,Ma,W.Y.:Automated known
problem diagnosis with event traces.In:Proceedings of EuroSys2006.(April2006)375–388
晋灵公不君（宣公二年） 原文： 晋灵公不君。厚敛以雕墙。从台上弹人，而观其辟丸也。宰夫胹熊蹯不熟，杀之，寘诸畚，使妇人载以过朝。赵盾、士季见其手，问其故而患之。将谏，士季曰：“谏而不入，则莫之继也。会请先，不入，则子继之。”三进及溜，而后视之，曰：“吾知所过矣，将改之。”稽首而对曰：“人谁无过？过而能改，善莫大焉。诗曰：‘靡不有初，鲜克有终。’夫如是，则能补过者鲜矣。君能有终，则社稷之固也，岂惟群臣赖之。又曰：‘衮职有阙，惟仲山甫补之。’能补过也。君能补过，衮不废矣。” 犹不改。宣子骤谏，公患之，使鉏麑贼之。晨往，寝门辟矣，盛服将朝。尚早，坐而假寐。麑退，叹而言曰：“不忘恭敬，民之主也。贼民之主，不忠；弃君之命，不信。有一于此，不如死也！”触槐而死。 秋九月，晋侯饮赵盾酒，伏甲将攻之。其右提弥明知之，趋登曰：“臣侍君宴，过三爵，非礼也。”遂扶以下。公嗾夫獒焉。明搏而杀之。盾曰：“弃人用犬，虽猛何为！”斗且出。提弥明死之。 初，宣子田于首山，舍于翳桑。见灵辄饿，问其病。曰：“不食三日矣！”食之，舍其半。问之，曰：“宦三年矣，未知母之存否。今近焉，请以遗之。”使尽之，而为之箪食与肉，寘诸橐以与之。既而与为公介，倒戟以御公徒，而免之。问何故，对曰：“翳桑之饿人也。”问其名居，不告而退。——遂自亡也。 乙丑，赵穿①攻灵公于桃园。宣子未出山而复。大史书曰：“赵盾弑其君。”以示于朝。宣子曰：“不然。”对曰：“子为正卿，亡不越竟，反不讨贼，非子而谁？”宣子曰：“呜呼!‘我之怀矣，自诒伊戚。’其我之谓矣。” 孔子曰：“董狐，古之良史也，书法不隐。赵宣子，古之良大夫也，为法受恶。惜也，越竞乃免。” 译文： 晋灵公不行君王之道。他向人民收取沉重的税赋以雕饰宫墙。他从高台上用弹弓弹人，然后观赏他们躲避弹丸的样子。他的厨子做熊掌，没有炖熟，晋灵公就把他杀了，把他的尸体装在草筐中，让宫女用车载着经过朝廷。赵盾和士季看到露出来的手臂，询问原由后感到很忧虑。他们准备向晋灵公进谏，士季说：“如果您去进谏而君王不听，那就没有人能够再接着进谏了。还请让我先来吧，不行的话，您再接着来。”士季往前走了三回，行了三回礼，一直到屋檐下，晋灵公才抬头看他。晋灵公说：“我知道我的过错了，我会改过的。”士季叩头回答道：“谁能没有过错呢？有过错而能改掉，这就是最大的善事了。《诗经》说：‘没有人向善没有一个开始的，但却很少有坚持到底的。’如果是这样，那么能弥补过失的人是很少的。您如能坚持向善，那么江山就稳固了，不只是大臣们有所依靠啊。
1、 Blindness is a very serious disability. 失明是非常严重的残疾。 2、 Though he is disabled, he is a gifted artist. 尽管身残疾 (的 )，他是一个有天赋的艺术家。 3、 person with a hearing and eyesight disability misses many things. 一位听力和视力残疾的人会错过很多东西。 4、 Beware of the love syndrome.当心恋爱综合症。 5、 Rosalyn had been there frequently in past years for treatment for infantile paralysis. 罗莎琳在过去的几年中频频来这里治疗小儿麻痹。 6、 Harris went on top in the last lap. 哈里斯在最后一圈跑到了最前面。 7、 He had a high ambition to be a headmaster. 他的抱负是想成为一名校长。 8、 I will love the ambitious for they can inspire me!我爱雄心壮志的人，因为他们能激励我！ 9、 We will have dictation today.我们今天要听写了。 10、 I wrote the letter at Sally's dictation . 我照萨利的口述写信。 11、 The campus is noisy today.今天校园里很吵。 12、 Do believe there is no best man, only much suitable one. 要相信没有最好男人，只有更适合的。 13、 Trees hid the entry of the cave. 洞穴的入口被树丛遮掩。 14、 Fresh air is beneficial to people's health. 新鲜空气对人的健康有好处。 15、 In other words, a classic fudge. 总之一句话，一派胡言。 16、 Mother reproached me for being too clumsy. 母亲责备我笨手笨脚。 17、 He used to be quiet, but now he is very outgoing. 他以前性格沉默少言，但现在很外向。 18、 How do you adapt to this new environment? 你要怎样适应这种新环境呢?。 19、 The bench often does duty for a table. 这条长凳经常当桌子用。 20、 The doctor told me to cut out meat for my fat. 由于肥胖，大夫叫我停止吃肉 21、 He applied his eye to the microscope. 他把眼睛贴近显微镜。 22、 She was out of breath from climbing the stairs. 爬楼梯使她上气不接下气的。 23、 A servant is known by his master's absence.主人不在就可以看出仆人的品行来。 24、 You are a milk-livered fellow!你真是一个胆小的家伙！ 25、 Thank you, my fellow colleagues. 谢谢，同事们。 26、 No joy without annoy. 没有无烦恼之快乐。 27、 I am really very annoyed about it. 我对此事真是很生气。 28、 I felt annoyance at being teased.我恼恨“别人”取笑我。 29、 I let go of all annoyance. 我放下所有烦恼。 30、 He has his faults, but all in all , he is a good guy. 他有缺点，但总的来说，他是不错的人。 单词拼读举例:Di sa bi li ty di sa bled syn drome in fan tile pa ra ly sis am bi tion am bi tious
Unit 3 Under the sea 【导语】捕鲸业是世界上古老的行业之一，它的历史发展和现状如何呢？ The whaling industry is one of the oldest industries in existence.It has undergone vast changes since its beginning，primarily due to the creation of the International Whaling https://www.doczj.com/doc/031037936.html,mercial whaling still continues throughout the world，but the whaling quotas are restricted by the commission，thereby helping conserve the whale populations. Whaling refers to hunting wh ales primarily for their oil，meat and bones.Whaling dates back to prehistoric times，most prevalent in Norway and Japan.The hunt became an industry in the 1600s in the Arctic regions，mostly by the Dutch and British.American colonists started whaling in the 1700s.Nantucket whalers were the first to kill a sperm whale，and the discovery of spermaceti in the whale's head made the sperm whale one of the most highly prized catches.Whaling ships set out from New England into the Pacific for extremely long voyages to hunt down these whales. Whaling industry has been a part of a variety of countries' industries.The following countries were the earliest pioneers in the whaling industry：England，France，Germany，Iceland，Japan，the Netherlands，Norway and the American colonies (although they were not a country at the time)．The following countries still practice whaling in some form or fashion：Canada，Greenland，the Grenadines，Iceland，Indonesia，Japan，the Netherlands，Norway，Russia and the United States. 【词海拾贝】 1．vast adj.广阔的；巨大的 2．primarily adv.首先；最初 3．commission n．委员会 4．commercial adj.商业的 5．quota n．配额 6．prevalent adj.盛行的 7．sperm whale 巨头鲸；抹香鲸 【问题思考】 1．What helps conserve the whale populations? _______________________________________________________ 答案：The whaling quotas.
如何翻译古文 学习古代汉语，需要经常把古文译成现代汉语。因为古文今译的过程是加深理解和全面运用古汉语知识解决实际问题的过程，也是综合考察古代汉语水平的过程。学习古代汉语，应该重视古文翻译的训练。 古文翻译的要求一般归纳为信、达、雅三项。“信”是指译文要准确地反映原作的含义，避免曲解原文内容。“达”是指译文应该通顺、晓畅，符合现代汉语语法规范。“信”和“达”是紧密相关的。脱离了“信”而求“达”，不能称为翻译；只求“信”而不顾“达”，也不是好的译文。因此“信”和“达”是文言文翻译的基本要求。“雅”是指译文不仅准确、通顺，而且生动、优美，能再现原作的风格神韵。这是很高的要求，在目前学习阶段，我们只要能做到“信”和“达”就可以了。 做好古文翻译，重要的问题是准确地理解古文，这是翻译的基础。但翻译方法也很重要。这里主要谈谈翻译方法方面的问题。 一、直译和意译 直译和意译是古文今译的两大类型，也是两种不同的今译方法。 1．关于直译。所谓直译，是指紧扣原文，按原文的字词和句子进行对等翻译的今译方法。它要求忠实于原文，一丝不苟，确切表达原意，保持原文的本来面貌。例如： 原文：樊迟请学稼，子曰：“吾不如老农。”请学为圃。子曰：“吾不如老圃。”（《论语?子路》） 译文：樊迟请求学种庄稼。孔子道：“我不如老农民。”又请求学种菜蔬。孔子道：“我不如老菜农。”（杨伯峻《论语译注》） 原文：齐宣王问曰：“汤放桀，武王伐纣，有诸？”（《孟子?梁惠王下》） 译文：齐宣王问道：“商汤流放夏桀，武王讨伐殷纣，真有这回事吗？（杨伯峻《孟子译注》） 上面两段译文紧扣原文，字词落实，句法结构基本上与原文对等，属于直译。 但对直译又不能作简单化理解。由于古今汉语在文字、词汇、语法等方面的差异，今译时对原文作一些适当的调整，是必要的，并不破坏直译。例如： 原文：逐之，三周华不注。（《齐晋鞌之战》） 译文：〔晋军〕追赶齐军，围着华不注山绕了三圈。
鞌之战选自《左传》又名《鞍之战》原文：楚癸酉，师陈于鞌(1)。邴夏御侯，逢丑父为右②。晋解张御克，郑丘缓为右(3)。侯日：“余姑翦灭此而朝食(4)”。不介马而驰之⑤。克伤于矢，流血及屦2 未尽∧6)，曰：“余病矣(7)！”张侯曰：“自始合(8)，而矢贯余手及肘(9)，余折以御，左轮朱殷(10)，岂敢言病吾子忍之！”缓曰：“自始合，苟有险，余必下推车，子岂＿识之(11)然子病矣！”张侯曰：“师之耳目，在吾旗鼓，进退从之。此车一人殿之(12)，可以集事(13)，若之何其以病败君之大事也擐甲执兵(14)，固即死也(15)；病未及死，吾子勉之(16)！”左并辔(17) ，右援拐鼓(18)。马逸不能止(19)，师从之，师败绩。逐之，三周华不注(20) 韩厥梦子舆谓己曰：“旦辟左右！”故中御而从齐侯。邴夏曰：“射其御者，君子也。”公曰：“谓之君子而射之，非礼也。”射其左，越于车下；射其右，毙于车中。綦毋张丧车，从韩厥，曰：“请寓乘。”从左右，皆肘之，使立于后。韩厥俛，定其右。逢丑父与公易位。将及华泉，骖絓于木而止。丑父寝于轏中，蛇出于其下，以肱击之，伤而匿之，故不能推车而及。韩厥执絷马前，再拜稽首，奉觞加璧以进，曰：“寡君使群臣为鲁、卫请，曰：‘无令舆师陷入君地。’下臣不幸，属当戎行，无所逃隐。且惧奔辟而忝两君，臣辱戎士，敢告不敏，摄官承乏。” 丑父使公下，如华泉取饮。郑周父御佐车，宛茷为右，载齐侯以免。韩厥献丑父，郤献子将戮之。呼曰：“自今无有代其君任患者，有一于此，将为戮乎”郤子曰：“人不难以死免其君，我戮之不祥。赦之，以劝事君者。”乃免之。译文1：在癸酉这天，双方的军队在鞌这个地方摆开了阵势。齐国一方是邴夏为齐侯赶车，逢丑父当车右。晋军一方是解张为主帅郤克赶车，郑丘缓当车右。齐侯说:“我姑且消灭了这些人再吃早饭。”不给马披甲就冲向了晋军。郤克被箭射伤，血流到了鞋上，但是仍不停止擂鼓继续指挥战斗。他说:“我受重伤了。”解张说:“从一开始接战，一只箭就射穿了我的手和肘，左边的车轮都被我的血染成了黑红色，我哪敢说受伤您忍着点吧！”郑丘缓说:“从一开始接战，如果遇到道路不平的地方，我必定（冒着生命危险）下去推车，您难道了解这些吗不过，您真是受重伤了。”daier 解张说:“军队的耳朵和眼睛，都集中在我们的战旗和鼓声，前进后退都要听从它。这辆车上还有一个人镇守住它，战事就可以成功。为什么为了伤痛而败坏国君的大事呢身披盔甲，手执武器，本来就是去走向死亡，伤痛还没到死的地步，您还是尽力而为吧。”一边说，一边用左手把右手的缰绳攥在一起，用空出的右手抓过郤克手中的鼓棰就擂起鼓来。（由于一手控马，）马飞快奔跑而不能停止，晋军队伍跟着指挥车冲上去，把齐军打得打败。晋军随即追赶齐军，三次围绕着华不注山奔跑。韩厥梦见他去世的父亲对他说:“明天早晨作战时要避开战车左边和右边的位置。”因此韩厥就站在中间担任赶车的来追赶齐侯的战车。邴夏说:“射那个赶车的，他是个君子。”齐侯说: “称他为君子却又去射他，这不合于礼。”daier 于是射车左，车左中箭掉下了车。又射右边的，车右也中箭倒在了车里。（晋军的）将军綦毋张损坏了自己的战车，跟在韩厥的车后说: “请允许我搭乗你的战车。”他上车后，无论是站在车的左边，还是站在车的右边，韩厥都用肘推他，让他站在自己身后——战车的中间。韩厥又低下头安定了一下受伤倒在车中的那位自己的车右。于是逢丑父和齐侯（乘韩厥低头之机）互相调换了位置。将要到达华泉时，齐侯战车的骖马被树木绊住而不能继续逃跑而停了下来。（头天晚上）逢丑父睡在栈车里，有一条蛇从他身子底下爬出来，他用小臂去打蛇，小臂受伤，但他（为了能当车右）隐瞒了这件事。由于这样，他不能用臂推车前进，因而被韩厥追上了。韩厥拿着拴马绳走到齐侯的马前，两次下拜并行稽首礼，捧着一杯酒并加上一块玉璧给齐侯送上去，
Unit 3 Underthesea 基础知识默写篇 一、分层单词 写作词汇 1. vt.放弃;遗弃;抛弃 2. vt.当场见到;目击 n.目击者;证人;证据 3. vi.& n.暂停;中止 4. vt.拖;拉;扯 5. vi.逃避;逃跑 vt.逃离 6. n.住所;住宿 7. n.关系;血缘关系;交往 8. adj.好的;整齐的;匀称的 9. adj.生动的;鲜明的;鲜艳的 10. adj.纯的;纯粹的;纯洁的 11. prep.在……对面 adj.相对的;相反的 12. vt.催促;极力主张;驱策 13. vi.思考 vt.映射;反射;思考 14. adj.意识到的;知道的 阅读词汇 1.jog vi.&vt. 2.dive vi.& n. 3.suck vt.& vi. 4.conservation n. 5.target n. 6.boundary n.
7.pension n. 8.annual adj. & n. 9.narrow adj. 10.shallow adj. 11.steep adj. 12.awesome adj. 13.seaside n.&adj. 14.telescope n. 15.teamwork n. 16.dimension n. 拓展词汇 1. n.深(度);深处→adj.深的adv. 深深地 2. adj.好吃的;可口的→ n.味道;品位;鉴赏力v.尝;品尝;有……的味道 3. adj.意识到的;知道的→ n.意识;认识 4. vi.思考vt.反射;思考→ n.反射;思考 5. adj.锐利的;锋利的;敏捷的→v.(使)变得锋利 6. vt.催促;极力主张;驱策→ n.紧急;迫切;催促→adj.紧急的;迫切的;催促的 7. vt.恐吓 vi.受惊吓→adj.害怕的 二、高频短语 1. 帮助(某人)摆脱困境或危难 2. 对……知道、明白;意识到…… 3. 举起;阻碍 4. 整理;收拾 5. 在此期间;与此同时 6. 靠近 7. upside down 8. (be) scared to death 9. aim at
《鞌之战》阅读答案（附翻译）原文及翻 译 鞌之战[1] 选自《左传成公二年（即公元前589年）》 【原文】 癸酉，师陈于鞌[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]。 【注释】 [1]鞌之战：春秋时期的著名战役之一。战争的实质是齐、晋争霸。由于齐侯骄傲轻敌，而晋军同仇敌忾、士气旺盛，战役以齐败晋胜而告终。鞌：通鞍，齐国地名，在今山东济南西北。 [2]癸酉：成公二年的六月十七日。师，指齐晋两国军队。陈，
列阵，摆开阵势。 [3]邴夏：齐国大夫。御，动词，驾车。御齐侯，给齐侯驾车。齐侯，齐国国君，指齐顷公。 [4]逢丑父：齐国大夫。右：车右。 [5]解张、郑丘缓：都是晋臣，郑丘是复姓。郤（x ）克，晋国大夫，是这次战争中晋军的主帅。又称郤献子、郤子等。 [6]姑：副词，姑且。翦灭：消灭，灭掉。朝食：早饭。这里是吃早饭的意思。这句话是成语灭此朝食的出处。 [7]不介马：不给马披甲。介：甲。这里用作动词，披甲。驰之：驱马追击敌人。之：代词，指晋军。 [8] 未绝鼓音：鼓声不断。古代车战，主帅居中，亲掌旗鼓，指挥军队。兵以鼓进，击鼓是进军的号令。 [9] 病：负伤。 [10]张侯，即解张。张是字，侯是名，人名、字连用，先字后名。 [11]合：交战。贯：穿。肘：胳膊。 [12]朱：大红色。殷：深红色、黑红色。 [13]吾子：您，尊敬。比说子更亲切。 [14]苟：连词，表示假设。险：险阻，指难走的路。 [15]识：知道。之，代词，代苟有险，余必下推车这件事，可不译。 [16]师之耳目：军队的耳、目（指注意力）。在吾旗鼓：在我们
Unit 3 under the sea 1.witness (1) v 当场见到，目击 . 在我昨天回家的路上路上我亲眼目睹一场事故。 (2) v表明，说明Her flushed（通红）face she felt. 她通红的脸表明他、她感到非常高兴。 (3) v 为…作证常与to 连用witness to 为某事作证说 He enter the room. 他作证说他看到那个人进入房间。 (4) n (C) “目击者，证人”常与to连用be a witness to 是…的目击者 The police found the witness to the murder case. 警察找到了那个谋杀案的目击者 (5) n (C,U) 证词，证据，证明give witness on behalf of 替…作证 The old man an accused person. 那位老人为被告作证。 2. sort (1) vt 把…分类,拣选 She is . 她正忙于给信件分类。 (2) sort out 整理（好） I 我已把信分好 (3) n 种类，类别 A hammer is .斧头是一种工具。 He’s the sort of person I really dislike. (4)词组sort of 颇为，有几分I feel . 我感觉有点生病了。 all sorts of 相当于all kinds of 3. accommodation (1) 房间，住所The accommodation of this hotel is scare. （不足） (2) 膳宿（常用复数） 我们今晚能找到旅馆住宿吗？Can we ____find accommodations at a hotel__ for tonight? (3) accommodate 向…提供住处，接纳(v) 相关短语：(1) make accommodations for 为…提供膳宿(2) book accommodation at a hotel 在旅馆预订房间 (4) accommodate …to = adapt… to 使…适应 You will have to accommodate yourself to the situation. 4. yell（1）v.叫喊。 （1）yell(out) at sb.朝某人大喊大叫 .她对淘气的孩子大喊大叫。 They yelled at him to stop. （2）n. /叫声，喊声 E.g. a yell of delight / warning 5. throw (1) 投，掷，扔，抛 Throw the ball to your younger brother. He was thrown into prison.被关进… (2) 匆忙或随便穿/脱 He threw a blanket over the injured man. 他匆忙给伤者披上毯子。
《鞌之战》阅读答案（附翻译） 《鞌之战》阅读答案（附翻译） 鞌之战[1] 选自《左传·成公二年（即公元前589年）》 【原文】 癸酉，师陈于鞌[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]。 【注释】 [1]鞌之战：春秋时期的著名战役之一。战争的实质是齐、晋争霸。由于齐侯骄傲轻敌，而晋军同仇敌忾、 士气旺盛，战役以齐败晋胜而告终。鞌：通“鞍”，齐
国地名，在今山东济南西北。 [2]癸酉：成公二年的六月十七日。师，指齐晋两国军队。陈，列阵，摆开阵势。 [3]邴夏：齐国大夫。御，动词，驾车。御齐侯，给齐侯驾车。齐侯，齐国国君，指齐顷公。 [4]逢丑父：齐国大夫。右：车右。 [5]解张、郑丘缓：都是晋臣，“郑丘”是复姓。郤（xì）克，晋国大夫，是这次战争中晋军的主帅。又称郤献子、郤子等。 [6]姑：副词，姑且。翦灭：消灭，灭掉。朝食：早饭。这里是“吃早饭”的意思。这句话是成语“灭此朝食”的出处。 [7]不介马：不给马披甲。介：甲。这里用作动词，披甲。驰之：驱马追击敌人。之：代词，指晋军。 [8]未绝鼓音：鼓声不断。古代车战，主帅居中，亲掌旗鼓，指挥军队。“兵以鼓进”，击鼓是进军的号令。 [9]病：负伤。 [10]张侯，即解张。“张”是字，“侯”是名，人名、字连用，先字后名。 [11]合：交战。贯：穿。肘：胳膊。 [12]朱：大红色。殷：深红色、黑红色。 [13]吾子：您，尊敬。比说“子”更亲切。
Unit 3 Under the sea 语言点 编稿：牛新阁审稿：王春霞 学习目标 重点词汇 annual witness accommodation opposite yell pause drag depth urge abandon target reflect scare awesome 重点短语 in the meantime be aware of ahead of ... to death help （...）out upside down 重点句型 It takes sb. some time/ ... to do sth.的变化 a time when... 知识讲解 重点词汇 annual 【原句回放】It was a time when the killer whales, or “killers” as they were then called, helped the whalers catch the baleen whales that were on their annual migration. 那个时期，虎鲸（当时被称为“杀手”）帮助捕鲸人在每年须鲸迁徙时捕捉须鲸。 【点拨】annual adj. 1. 每年的，一年一次的 the annual output 年产量an annual report 年度报告 Steel output reached an annual figure of one million tons. 钢的年产量达到100万吨。 2. 按年度计算的 the annual income 年收入the annual rainfall 【拓展】annually adv. 每年地，年度地 witness 【原句回放】I thought, at the time, that this was just a story but then I witnessed it with my own eyes many times. 当时我以为这只是一个故事罢了，但是后来我亲眼见过多次。 【点拨】witness vt.& vi.亲眼看见，目睹，作证； n.见证人；目击者（与of连用） We were witnessing the most important scientific development of the century. 我们正目睹着本世纪最重要的科学发展。 We witnessed great changes in the city. 我们见证了这个城市的巨大变化。 The police found the witness of the murder case. 警察找到了那起谋杀案的证人。 There was no witness at the scene of the accident. 在事故现场没有目击证人。 【拓展】常见搭配：witness to (doing...)为……作证 bear / give witness to 为......作证 in witness of 作为......的证据 a living witness to 活生生的证人 witness stand 证人席(美)＝witness box (英) He witnessed to having seen the man enter the building.
模块7各单元词汇和短语复习 Unit 1 Living Well Part One 根据首字母或汉语提示写出完整的单词: 1. An unexpected accident made Sang Lan a girl with a physical d____________, but she never gave up. 2. We often observe the tiny cells with m______________ in our biology classes. 3. The production of iron and steel is the most important i______________ of the city. 4. Taiwan is part of China and not an i_______________ state. 5. I have passed all the exams and I am waiting to get the graduation c_______________. 6. A place is a______________ if it is possible to reach it. 7. I was not alone on the journey. Instead, I had so many c________________. 8. You can refer to old people in general as the _______________. 9. When something can help people or improve their lives, we say it is ______________ to people. 10. When the disabled meet with difficulty, we should do what we can to give them a___________. 11. One of his ________________ (志向) is to become a world-wide famous pop singer. 12. He was _____________(笨拙的) with a tool. 13. The patient’s _______________(呼吸) grew stronger and stronger. 14. Who took his place and controlled the company during his ________________ (不在) ? 15. I’m going to give some suggestions to this famous ________________(建筑师). 16. A man’s _______________（尊严）doesn’t depends on his wealth but on his character. Part Two 一、词形变换（用所给词的适当形式填空） 1. The ______________ is good at ______________ TV plays from the stories he reads about or hears. (adapt) 2. The country used to be _____________ on Britain in many ways, but now it has become absolutely_______________. (depend) 3. We have ___________ a lot from the co-operation and I’m sure it will continue to be ________ to both of us. (benefit) 4. Her _____________ lecture ____________ all of us. We won’t forget her ____________. (encourage) 5. ______________ people should be treated equally in spite of their ______________. (disability) 6. You were _____________ yesterday, Tom. Can you tell me the reason for you _____________? (absent) 7. The ______________ serving the passengers on the train is of good_______________. (conduct) 8. ________________ countries pay much attention to the development of ________________. (industry) 二、翻译句子 1. 应该给残疾人尽可能多的鼓励和援助。 ______________________________________________________________________________ 2. 换句话说，这些措施对我们的工业发展是有益的。 ______________________________________________________________________________ 3. 总之，在学校寄宿(board)能帮助学生学会独立。 ______________________________________________________________________________
左传《齐晋鞌之战》原文+翻译+注释 楚癸酉，师陈于鞌(1)。邴夏御侯，逢丑父为右②。晋解张御克，郑丘缓 为右(3)。侯日：“余姑翦灭此而朝食(4)”。不介马而驰之⑤。克伤于矢， 流血及屦2未尽∧?6)，曰：“余病矣(7)！”张侯曰：“自始合(8)，而矢贯余手 及肘(9)，余折以御，左轮朱殷(10)，岂敢言病？吾子忍之！”缓曰：“自始合，苟有险，余必下推车，子岂＿识之(11)？然子病矣！”张侯曰：“师之耳目，在 吾旗鼓，进退从之。此车一人殿之(12)，可以集事(13)，若之何其以病败君之大事也？擐甲执兵(14)，固即死也(15)；病未及死，吾子勉之(16)！”左并辔(17) ，右援拐?鼓(18)。马逸不能止(19)，师从之，师败绩。逐之，三周华不注(20) 韩厥梦子舆谓己曰：“旦辟左右！”故中御而从齐侯。邴夏曰：“射其御者，君子也。”公曰：“谓之君子而射之，非礼也。”射其左，越于车下；射其右，毙于车中。綦毋张丧车，从韩厥，曰：“请寓乘。”从左右，皆肘之，使立于后。韩厥俛，定其右。逢丑父与公易位。将及华泉，骖絓于木而止。丑父寝于轏中，蛇出于其下，以肱击之，伤而匿之，故不能推车而及。韩厥执絷马前，再拜稽首，奉觞加璧以进，曰：“寡君使群臣为鲁、卫请，曰：‘无令舆师陷入君地。’下臣不幸，属当戎行，无所逃隐。且惧奔辟而忝两君，臣辱戎士，敢告不敏，摄官承乏。”丑父使公下，如华泉取饮。郑周父御佐车，宛茷为右，载齐侯以免。韩厥献丑父，郤献子将戮之。呼曰：“自今无有代其君任患者，有一于此，将为戮乎？”郤子曰：“人不难以死免其君，我戮之不祥。赦之，以劝事君者。”乃免之。 在癸酉这天，双方的军队在鞌这个地方摆开了阵势。齐国一方是邴夏为齐侯赶车，逢丑父当车右。晋军一方是解张为主帅郤克赶车，郑丘缓当车右。齐侯说:“我姑且消灭了这些人再吃早饭。”不给马披甲就冲向了晋军。郤克被箭射伤，血流到了鞋上，但是仍不停止擂鼓继续指挥战斗。他说:“我受重伤了。”解张说:“从一开始接战，一只箭就射穿了我的手和肘，左边的车轮都被我的血染成了黑红色，我哪敢说受伤？您忍着点吧！”郑丘缓说:“从一开始接战，如果遇到道路不平的地方，我必定（冒着生命危险）下去推车，您难道了解这些吗？不过，您真是受重伤了。”daier解张说:“军队的耳朵和眼睛，都集中在我们的战旗和鼓声，前进后退都要听从它。这辆车上还有一个人镇守住它，战事就可以成功。为什么为了伤痛而败坏国君的大事呢？身披盔甲，手执武器，本来就是去走向死亡，伤痛还没到死的地步，您还是尽力而为吧。”一边说，一边用左手把右手的缰绳攥在一起，用空出的右手抓过郤克手中的鼓棰就擂起鼓来。（由于一手控马，）马飞快奔跑而不能停止，晋军队伍跟着指挥车冲上去，把齐军打得打败。晋军随即追赶齐军，三次围绕着华不注山奔跑。
第5讲Under the sea 词汇篇 __________________________________________________________________________________ __________________________________________________________________________________ 1.熟练掌握重点单词及其用法； 2.能够熟练运用重点短语和句型。 一. 重点词汇 1.annual adj. 每年的；按年度计算的n. 年刊；年鉴 [重点用法] annually adv. 年年地，每年地 [典例] 1) an annual income. 年收入 2) an annual report年度报告 3) Premier Wen Jiabao noted that the two most important problems would be previous to anything else in the government annual report.温家宝总理在政府年度报告中指出要优先解决这两大问题。 2.witness n. 目击者；证人；证据vt. 当场见到；目击 [典例] 1) He is the witness to the accident. 事故的目击者 2) This old auditorium has witnessed many ceremonies. 这个古老的礼堂内举行过许多次典礼。 3.accommodation住所 [重点用法] accommodate v.向...提供，容纳，调和；适应 accommodation address临时通讯处 accommodation allowance膳宿津贴 [典例] 1) The high cost of accommodation makes life difficult for students in London. 由于住宿费用昂贵，伦敦的学生感到生活困难。 2) The university offers excellent accommodation for summer visitors. 这所大学为夏季来访者提供了很好的住宿。 4.abandon vt. 放弃；遗弃；抛弃n. 放任，狂热 [重点用法] abandon oneself to sth./doing sth. 沉溺于 abandon …to sb. 把……舍弃给…... with abandon放任地；放纵地；纵情地 [典例]
BOOK7 Unit1单词练习题 一．根据所给的首字母写出单词的正确形式。 1.What we choose and decide forms our life, but a_______ decides our choice and decision. 2.We should design more websites that are both technically a________ and also usable for people with disabilities. 3.As is known to all, Mo Yan was awarded the 2012 Nobel Prize for l_________. 4.The whole class c________ me on getting the first prize in the English competition. 5.Recently I watched a cartoon a________ from the famous drama by Shakespeare. 二．根据句意用括号内所给单词的适当形式填空。 1.It is known to all that fresh air is _____ to our health and the new park ______ us all, so we should keep it clean.( benefit ) 2.The little boy made up a tale for his ______ ( absent ) from school. 3.Praise acts as an _____ to the players, and therefore they will feel _____ and get the ______ to continue and improve their performance. ( encourage ) 4.The ______ girls swims well in spite of her ______. (disable ) 5.My brother ______ from a well—known American university. My parents attended his ______ ceremony yesterday. ( graduate )