An AOP Case with Static and Dynamic Aspects
USB Type-C 规范1.2(中文版)
知识产权声明
THIS SPECIFICATION IS PROVIDED TO YOU “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE. THE AUTHORS OF THIS SPECIFICATION DISCLAIM ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY PROPRIETARY RIGHTS, RELATING TO USE OR IMPLEMENTATION OF INFORMATION IN THIS SPECIFICATION. THE PROVISION OF THIS SPECIFICATION TO YOU DOES NOT PROVIDE YOU WITH ANY LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS.
预发行行业审查公司提供反馈
Revision History.......................................................................................................................14
LIMITED COPYRIGHT LICENSE: The USB 3.0 Promoters grant a conditional copyright license under the copyrights embodied in the USB Type-C Cable and Connector Specification to use and reproduce the Specification for the sole purpose of, and solely to the extent necessary for, evaluating whether to implement the Specification in products that would comply with the specification.
Ultrastructural and funnctional aspects of static and motile systems in two taxa
Protistology Protistology 6 (3), 139–146 (2010)Ultrastructural and functional aspects of staticand motile systems in two taxa of the Alveolata:Dinoflagellata and CiliataKlaus Hausmann and Norbert HülsmannDivision of Protozoology, Institute of Biology/Zoology, Free Universityof Berlin, Berlin, GermanysummaryIn this synopsis we review some, for a long time well known, ultrastructural andfunctional aspects of static and motile systems in dinoflagellates and ciliates, i. e.,alveolar (=amphiesmal) plates, contraction-elongation and coiling phenomena,piston activities, cell contractions, peduncle and tentacle feeding. It is our effortto point to the existence of a rich source of observations on structural features andcognitions on functions in unicellular organisms in the literature which are in dangerto be forgotten.Key words: dinoflagellates, ciliates, alveolar/amphiesmal plates, body contraction/elongation, peduncle/tentacle feedingSeveral decades ago the idea that dinoflagellates and ciliates might have a common root was of more heretical nature. The time was not ripe to accept such a possibility, although there had already been ultrastructural und cytochemical observations that certain ciliates possess plates in their alveoli, as most of the dinoflagellates do in their amphiesmata. Motile phenomena in dinoflagellates such as cell contraction or piston contraction and elongation were never discussed in the context of stalk or body contraction and their similarity to the elongation of ciliates; even such similar processes as feeding by a peduncle and feeding by tentacles or by cytopharyngeal baskets were not properly compared.Today it is widely accepted that the phylum Alveolata includes protist taxa such as Dinoflagellata, Ciliophora, Apicomplexa as well as Perkinsozoa. Using structural and molecular methods, it has been convincingly shown that these protistan taxa originate from a common ancestor (Hausmann et al., 2003). The name-giving structures are subplasmalemmal alveoli/amphiesmata. These flattened vacuoles are arranged in a mosaic-like pattern and nearly always exhibit a species-specific arrangement. A first review on the general relationships between flagellates and ciliates was published by Lee and Kugrens in 1992.A lveolAr (=AmphiesmAl) plAtesIn armoured dinoflagellates, the amphiesmata contain so called thecal plates (Fig. 1) which consist of a non-cellulosic glucan (Nevo and Sharon, 1969; Dodge and Crawford, 1970) but not of proteins.© 2010 by Russia, Protistology· 140 Klaus Hausmann and Norbert H ülsmannAlveolar plates are relatively seldom found in ciliates (Fig. 2) and normally the alveoli are electron lucent. Alveolar plates of ciliates do not consist mainly of polysaccharides. At least two different varieties of plates are known: In the alveoli of e.g. Coleps , the plates are composed of a polysaccharide matrix incrusted by calcium phosphocarbonate (Faur é-Fremiet et al., 1968). In contrast, the plates in Euplotes consist mainly of protein with a fine polysaccharide coating (B öhm and Hausmann 1981). Such plates are thought to give the cortex of dinoflagellates and ciliates rigidity and thus also protection (Nobili, 1967; Walker, 1975; Hausmann and Kaiser, 1979).C ontrACtion -elongAtion -meChAnisms inflAgellAtesBesides this more structural, static similarity between dinoflagellates and ciliates, a highly dynamic phenomenon can be found in these two taxa, i.e., a contraction-elongation-mechanism in certain species of both groups which is astoundingly similar, if not identical.The basis for the following comparison is the motile behaviour of a species of the dinoflagellate genus Erythropsidinium (Erythropsis ). These flagella-tes, which are currently the focus of attention in the context of phylogenetics (Gomez, 2008), have been the subject of interest for a long time due to a spectacular organelle complex (an eye-like stigma) termed ocelloid (Fig. 3). It is a rather intricate structure which resembles the compound eye of arthropods in several respects (Greuet, 1967, 1968, 1987). Although there is thus far no experimental evidence at all that this structure is involved in photoreception, this rather amazing organelle has attracted a lot of attention. Perhaps for this reason, however, another significant structure of thesedinoflagellates has been somewhat neglected: Its highly dynamic posterior end, called tentacle or piston.This tube-like cell extension can elongate to more than 10fold of its shortest stage (Fig. 3). The elongation-contraction cycle is a very rapid process which lasts only about one second in some species. The cell performs this movement continuously except for occasional short interruptions. Although it has been speculated that this piston is somehow involved in cell locomotion (Greuet, 1987; Gomez, 2008), there is no convincing proof for this explana-tion thus far.When studying this movement in detail by frame-by-frame analysis of video sequences (Haus-mann, 2006), it becomes obvious that the elonga-tion and the contraction of the tentacle differ from each other clearly and unambiguously: elongation takes twice or three times as long as the extremely rapid contraction (Fig. 3).But what might be the cell biological purpose of this activity be? To answer this question, itFig. 1. A – The armoured dinoflagellate Peridiniumtabulatum with thecal plates (tp); B – plasmamem-brane (pm) underlaid by amphiesmata (am) which contain amphiesmal (= alveolar = thecal) plates(ap) (from Hausmann, 2008).Fig. 2. Alveolar plates in the ciliate Euplotes vannus . A – silverline system showing the regular arrange-ment of alveoli (light microscopy); B – alveolar plates inside the alveoli (electron microscopy); C – 3D-reconstruction of the pellicle. ialm - inner alveolar membrane, oalm - outer alveolar mem-brane, ap - alveolar plates, pm - plasmamembrane (from Hausmann et al., 2003).· 141 Protistologymay be helpful to look for comparable activities in other flagellates. So far nothing has been published for free-living flagellates which could be compared directly with the piston movement of Erythropsidinium. Noctiluca scintillans, a hete-rotrophic, unarmoured (i.e. no plates in the amphi-esmata) dinoflagellate, possesses likewise a tentacle used for food acquisition. However, this appendage moves in a completely different way, slowly swinging to and from, and cannot be compared with the tentacular behaviour of Erythropsidinium (Greuet, 1987).C oiling of elongAted orgAnelles in flAgellAtes And CiliAtesA comparable rapid contraction of a long cell process can be observed in the haptonema of several prymnesiomonad (haptophyte) flagellates (Leadbeater, 1971). However, in corresponding cases the cell process does not shorten during the contraction; the structure retains its length and only coils or bends (Fig. 4) (Kawachi et al., 1991; Inouye and Kawachi, 1994; Nakayama et al., 2005). The mechanism of this movement is still unclear.Fig. 3.Erythropsidinium pavillardi. A – habitus (n - nucleus, o - ocelloid, p – piston); B – illustration of the elongation-contraction cycle of the piston, based on a one second lasting video sequence (from Hausmann, 2006); C – 3D-reconstruction of the ultrastructure of the piston of Erythropsis (er - endoplasmic reticulum, mi -mitochondrion, mtl - microtubular lamellae, myo - myonemes) (after Greuet).· 142At this point one should have a look at other representatives of Alveolata and examine whether haptonema-like contractions might occur here or not. The first candidates are the ciliates; the stalk contractions of peritrich ciliates such as Vorticella or Carchesium immediately come to mind (Amos, 1972; Allen, 1973a, 1973b; Amos et al., 1975). However, this is the same situation as it is for the haptonema, namely coiling instead of shortening (Fig. 5), and cannot be compared with piston contractions.C ontrACtion -elongAtion -meChAnisms in CiliAtesLooking further for contraction activities in ciliates, the body contraction of heterotrichs, for instance of species belonging to Stentor , might reflect a comparable situation. This contraction-elongation system was studied in great detail in the 1970s (Bannister and Tatchell, 1968, 1972; Huang and Pitelka, 1973). It was demonstrated that microtubular lamella, myonemes (bundles of 4 nm filaments), and ER cisternae, which are arranged in a highly organized, characteristic spatial pattern, are the cellular constituents responsible for the contraction and elongation of these ciliates. This situation is true in general for contractile hete-rotrichs such as Spirostomum ambiguum (Hawkes and Holberton, 1974, 1975) and Eufolliculina uhligi (Fig. 6) (Mulisch et al., 1981).It has been shown that the myonemes are responsible for the rapid (mere milliseconds) contraction of the cells. During contraction, these filaments change their conformation and thicken to 10-12 nm, becoming shorter and tubular. This conformational alteration does not require ATP, but it is highly influenced by the concentration of calcium. This suggests that the ER cisternae adjacent to the myonemes serve as a site of calcium sequestration.The elongation of the ciliate (which lasts several seconds) is caused by an active gliding of the microtubular lamellae relative to each other, possibly with dynein serving as a motor protein.p iston ACtivity in wArnowiid dinoflAgellAtes What is the ultrastructure of Erythropsidinium ’s piston? In an early study, Greuet (1967) described the constituents of the tentacle in great detail. The nature and arrangement of the cellular structures involved in the contraction-elongation process in Erythropsidinium are the same as found for heterotrich ciliates: microtubules, myonemes and ER cisternae (Fig. 6). It is not surprising that the phenomena are also the same: Extremely rapid contraction and relatively slow extension of the piston.The piston activity of the dinoflagellate Erythro-psidinium has never been discussed in articles on the contractile cortex of the heterotrich ciliates whichKlaus Hausmann and Norbert H ülsmannFig. 4. Fig. 4. Chrysochromulina parva with uncoiled(A, B), coiling (C) and coiled haptonema (D). f -flagellum, h -haptonema (from John et al., 2002). Fig. 5. Elongated (A) and coiled stalk of the ciliate Vorticella (B) (courtesy of Peter Sitte, Freiburg,Germany).· 143Protistology were published somewhat later. Obviously the chasm between dinoflagellates and ciliates seemed so deep that none of the zoologically oriented ciliatologists assumed that it was worthwhile to discuss the situation in flagellates perhaps they were not even aware of the ultrastructural details of botanical unicellular organisms. Nowadays we are in a somewhat better situation. Hopefully!C ell ContrACtion in leptodisCinAedinoflAgellAtesThere are several other motility phenomena known from protists (Cachon and Cachon, 1982). One example is the body contraction e.g. of the marine Leptodiscinae, a group of marine dinoflagellates. These anteroposteriorly flattened flagellates are able to contract rapidly (Fig. 7). The structures responsible for this contraction consist of a layer of parallel filaments located beneath the cell membrane of certain parts of the body (Cachon and Cachon, 1984). The filaments are of non-actin type. They appear helically coiled and doubly twisted, and form tubular structures when contracted. ERcisternae traverse the filamentous layer regularly (Fig. 7). According to the cell biological tenor of this study, the authors discuss pleasantly and correctly that this situation is remarkably similar to that of the stalks of the peritrich ciliates. However, they make no statement about the phylogenetic significance and implications of these results. The time was not yet ripe for this aspect.f eeding by A pedunCle in dinoflAgellAtes = feeding by A tentACle in suCtoriAn CiliAtes ?The structure and mode of function of suctorian tentacles was studied in great detail during the 1960s (Rudzinska, 1965; Bardele, 1972). The main constituents of a tentacle are microtubules arranged helically in two concentric, tube-shaped arrays, actin-like microfilaments and different types of vesicles. The following scenario is proposed to occur during food uptake by suctorians (Fig. 8) (Rudzinska, 1965; Bardele, 1974; Tucker, 1974): Prey organisms which happen to come into contactwith their haptocysts (type of extrusomes) becomeFig. 6. The ciliate Stentor sp. elongated (A) and con-tracted (B) (courtesy of Heinz Schneider, Landau,Germany); C – 3D-reconstruction of the cortex of Stentor coeruleus . er - endoplasmic reticulum, mtl - microtubular lamellae, myo - myoneme (after Huang and Pitelka).Fig. 7. The leptodiscin dinoflagellate Cymbodinium elegans . A – body contraction; B – reconstruction of the cell region responsible for the body con-traction ( in A); al – alveolus (= amphiesma), er - endoplasmic reticulum, mi - mitochondrion, myo - myoneme, pm - plasmamembrane (afterCachon and Cachon).· 144stuck at the knob-like ends of involved tentacles. The cell membrane of the captured prey is ruptured at the contact zone. Vesicles then stream upward (centrifugally) along the peripheral tube of the tentacle and fuse with the membrane of the tentacle tip, providing the membrane material necessary for phagocytosis. Concomitantly, the membrane of the tip invaginates into the inner tube of the tentacle and prey cytoplasm rapidly streams down with it. When the invaginating membrane reaches the end of the inner tube, food vacuoles are pinched off. Arm-like bridges – most possibly dyneins – connecting the tentacle microtubules with the invaginating membrane are thought to be involved in the generation of the motive force for ingestion. A genuine suction act – implicating the generation of pressure differences – is highly unlikely (Rudzinska, 1973).In our opinion, the structural and functional basis of the ‘peduncle feeding’ visible in certain heterotrophic dinoflagellates, which was studied in detail almost one decade later (Schnepf et al., 1985), is highly similar, if not the same, as in ‘tentacle feeding’ in suctorian ciliates (Fig. 9) in that in both cases the host plasmalemma is pierced by the feeding organelle but not ingested as a membrane. As a consequence of this process there is only one membrane, namely that of the food vacuole, between the cytoplasm of the predator and the ingested cytoplasm, in dinoflagellates as well as in ciliates.However, the situation in dinoflagellates has been interpreted speculatively in a way that cannot be compared with the interpretation accepted for suctorians. Moreover, a new, somewhat delusive terminus for peduncle feeding has been created without convincing experimental proof: myzocy-tosis (i.e. phagocytosis by sucking) (Schnepf and Deichgr äber, 1984; Schnepf and Elbr ächter, 1992). Despite the fact that more then ten years ago a suction activity in this type of phagocytosis was ruled out (Rudzinska, 1973), this new terminus has unfortunately been accepted and adopted by botanists and protistologists, including the taxonomic designation Myzozoa for the taxon comprising dinoflagellates and apicomplexans (Cavalier-Smith and Chao, 2004).It must be mentioned that in none of the feeding organelles, peduncle nor tentacle, has an actual suction, i.e. the creation of low pressure inside the feeding cell, been demonstrated. Consequently, both termini, suctorians as well as myzocytosis, are misleading and should be substituted by neutral terms.In closing, it should be mentioned that the cytopharyngeal baskets which are used by nasso-phorean ciliates for phagocytosis (Tucker, 1968, 1972, 1978; Hausmann and Peck, 1978, 1979) are structurally and functionally the same as the tentacles of suctorians and thus, in our opinion, as the peduncles of dinoflagellates.Klaus Hausmann and Norbert H ülsmannFig. 8. Feeding mechanism of a suctorian ciliate (A – C). al - alveolus, fv - food vacuole, mt - microtubules, pm- plasmamembrane, pr - prey, t - tentacle (from Hausmann et al., 2003).· 145Protistology ReferencesAllen R.D. 1973a. Contractility and its control in peritrich ciliates. J. Protozool. 20, 25–36.Allen R.D. 1973b. Structures linking the my-onemes, endoplasmic reticulum and surface mem-branes in the contractile ciliate Vorticella . J. Cell Biol. 56, 559–579.Amos W.B. 1972. Structure and coiling of the stalk in the peritrich ciliates Vorticella and Carche-sium . J. Cell Sci. 10, 95–122.Amos W.B., Routledge L.M. and Yew F.F. 1975. Calcium binding proteins in a vorticellid contractile organelle. J. Cell Sci. 19, 203–213.Bannister L.M. and Tatchel E.C. 1968. Con-tractility and the fiber systems of Stentor coeruleus . J. Cell Sci. 3, 295–308.Bannister L.M. and Tatchel E.C. 1972. Fine structure of the M fibres in Stentor before and after shortening. Exp. Cell Res. 73, 221–226.Bardele C.F. 1972. A microtubule model for ingestion and transport in the suctorian tentacle. Z. Zellforsch. 126, 116–134.Bardele C.F. 1974. Transport of materials in the suctorian tentacle. Symp. Soc. exp. Biol. 28, 191–208.B öhm P. and Hausmann K. 1981. Cytochemicalinvestigations of the alveolar plates of the Euploti-Fig. 9. Peduncle feeding in a dinoflagellate. f - flagellum, fv - food vacuole, mt - microtubules, n - nucleus, p - peduncle, pr - prey, pu - pusule (after Schnepf et al.).dae (Ciliophora, Hypotrichida). Protoplasma. 106,309–316.Cachon J. and Cachon M. 1982. Movement by non-actin filament mechanisms. BioSystems. 14, 313–326.Cachon J. and Cachon M. 1984. An unusual mechanism of cell contraction: Leptodiscinae dino-flagellates. Cell Motil. 4, 41–55.Cavalier-Smith T. and Chao E.E. 2004. Protal-veolate phylogeny and systematics and the origins of Sporozoa and dinoflagellates (phylum Myzozoa nom. nov.) Europ. J. Protistol. 40, 185–212.Dodge J.D. and Crawford R.M. 1970. A survey of thecal fine structure in the Dinophyceae. Bot. J. Linn. Soc. 63, 53–67.Faur ét-Fremiet E., Andr é J. and Ganier M.-C. 1968. Calcification t égumentaire chez les cili és du genre Coleps Nitsch. J. Microscopie. 7, 693–704.Gomez F. 2008. Erythropsidinium (Gymnidini-ales, Dinophyceae) in the Pacific Ocean, a unique dinoflagellate with an ocelloid and a piston. Europ. J. Protistol. 44, 291–298.Greuet C. 1967. Organisation ultrastructu-rale du tentacule d’Erythropsis pavillardi Kofoid et Swezy, P éridinien, Warnowiidae Lindemann. Protistologica. 3, 335–346.Greuet C. 1968. Organisation ultrastructurale de l’ocelle de deux P éridiniens Warnowiidae, Eryth-ropsis pavillardi Kofoid et Swezy et de Warnovia pulchra Schiller. Protistologica. 4, 209–230.Greuet C. 1987. Complex organelles. In: The biology of dinoflagellates (Ed. Taylor F.J.R.), Bo-tanical Monographs 21. Blackwell Science Publish-ers, Oxford. pp 119–142.Hausmann K. 2006. Plankton der Meere – Einzellige Kostbarkeiten aus ozeanischem Ober-fl ächenwasser. Teil 1: Diatomeen, Dinoflagel-laten, Foraminiferen, Ciliaten. Mikrokosmos. 95, 298–304.Hausmann K. 2008. Dinoflagellaten mit bi-zarren Ausw üchsen. Mikrokosmos. 97, 341–345.Hausmann K. and Kaiser J. 1979. Arrangement and structure of plates in the cortical alveoli of the hypotrich ciliate, Euplotes vannus . J. Ultrastruct. Res. 67, 15–22.Hausmann K. and Peck R.K. 1978. Microtu-bules and microfilaments as major components of a phagocytic apparatus: The cytopharyngeal basket of the ciliate Pseudomicrothorax dubius . Differentia-tion. 11, 157–167.Hausmann K. and Peck R. K. 1979. The mode of function of the cytopharyngeal basket of the cili-ate Pseudomicrothorax dubius . Differentiation. 14, 147–158.· 146Address for correspondence: Klaus Hausmann. Division of Protozoology, Institute of Biology/Zoology, Free University of Berlin, D - 14195 Berlin, Germany, e-mail: hausmann@zedat.fu-berlin.deHausmann K, H ülsmann N. and Radek R. 2003. Protistology, 3rd edition. Schweizerbart’sche Verlagsbuchhandlung, Stuttgart.Hawkes R.B. and Holberton D.V. 1974. Mone-mal contraction of Spirostomum . I. Kinetics of contraction and relaxation. J. Gen. Physiol. 84, 225–236.Hawkes R.B. and Holberton D.V. 1975. Myone-mal contraction of Spirostomum . II. Some mechani-cal properties of the contractile apparatus. J. Gen. Physiol. 85, 595–602.Huang B. and Pitelka D.R. 1973. The contractile process in the ciliate Stentor coeruleus . J. Cell Biol. 57, 704–728.Inouye I. and Kawachi M. 1994. The haptoema. In: The haptophyte algae (Eds. Green J.C. and Leadbeater B.S.C.) Clarendon Press, Oxford. pp 73–89.John D.M., Whitton B.A. and Brook A.J. (Eds.) 2002. The freshwater algal flora of the British isles. University Press, Cambridge.Kawachi M., Inouye I., Maeda O. and Chihara M. 1991. The haptonema as a food-capturing device: observations on Chrysochromulina hirta (Prymne-siophyceae). Phycologia. 30, 563–573.Leadbeater B.S.C. 1971. Observations by means of cine photography on the behaviour of the hapto-nema in plankton flagellates of the class Haptophyc-eae. J. Marine Biol. Assoc UK. 51, 207–217.Lee R.E. and Kugrens, P. 1992. Relationship between the flagellates and the ciliates. Microbiol. Rev. 56, 529–542.Mulisch M., Barthlott W. and Hausmann K. 1981. Struktur und Ultrastruktur von Eufolliculina spec. – Schw ärmer und sessiles Stadium. Protisto-logica. 17, 285–312.Nakayama T., Yoshida M., No öl M.-H., Ka-wachi M. and Inouye I. 2005. Ultrastructure and phylogenetic position of Chrysoculter rhomboideus gen. et sp. nov. (Prymnesiophyceae), a new flagellate haptophyte from Japanese coastal waters. Phycolo-gia. 44, 369–383.Nevo Z. and Sharon N. 1969. The cell wall of Peridinium westii , a non cellulosic glucan. Biochim. Biophys. Acta. 173, 161–175.Nobili R. 1967. Ultrastructure of the fusion re-gion of conjugating Euplotes (Ciliata, Hypotrichida). Monitore Zool. Ital. (N. S.) 1, 73–89.Rudzinska M.A. 1965. The fine structure and function of the tentacle in Tokophrya infusionum . J. Cell Biol. 25, 459–477.Rudzinska M.A. 1973. Do Suctoria really feed by suction? Bioscience. 23, 87–94.Schnepf E. and Deichgr äber G. 1984. “Myzo-cytosis”, a kind of endocytosis with implications to compartmentation in endosymbiosis. Observations in Paulsenella (Dinophyta). Naturwissenschaften 71, 218–219.Schnepf E. and Elbr ächter M. 1992. Nutritional strategies in dinoflagellates. A review with emphasis on cell biological aspects. Europ. J. Protistol. 28, 3–24.Schnepf E., Deichgr äber G. and Drebes G. 1985. Food uptake and the fine structure of the di-nophyte Paulsenella sp., an ectoparasite of marine diatoms. Protoplasma. 124, 188–204.Tucker J.B. 1968. Fine structure and function of the cytopharyngeal basket in the ciliate Nassula . J. Cell Sci. 3, 493–514.Tucker J.B. 1972. Microtubule-arms and propulsion of food particles inside a large feeding organelle in the ciliate Phascolodon vorticella . J. Cell Sci. 10, 883–903.Tucker J.B. 1974. Microtubule arms and cy-toplasmic steaming and microtubule bending and stretching of intertubule links in the feeding tentacle of the suctorian ciliate Tokophrya . J. Cell Biol. 62, 424–436.Tucker J.B. 1978. Endocytosis and streaming of highly gelated cytoplasm alongside rows of arm-bearing microtubules in the ciliate Nassula . J. Cell Sci. 29, 213–232.Walker G.K. 1975. Observations on a unique cortical network in the hypotrich ciliates Euplotes vannus . Protistologica. 11, 275–278.Klaus Hausmann and Norbert H ülsmann。
JAVA程序员常用英语
JAVA程序员常用英语源自：ZTE♥李保民♥SIFE 261干程序员这行实在是离不开英语，干程序员是一项很辛苦的工作，要成为一个高水平的程序员尤为艰难.这是因为计算机软件技术更新的速度越来越快，而这些技术大多来源于英语国家，我们在引进这些技术时往往受到语言障碍的制约，严重影响到对新技术的理解和消化.首先编程本身就依赖于英语，虽然现在技术的发展，可以使得某些开发工具在变量名和字段名中支持中文,但还未发现能够完全使用中文的编程语句.这并不代表我们英语差，就不能编程了，下面提供一点入门级的程序员常用英语，以此为开始,迈出我们学习英语的第一步,努力学习英语吧，英语会使你的编程事半功倍.下面是JAVA语言常用英语汇总，java常用名词解释，计算机常用英语汇总。
JAVA语言常用英语汇总：A. array数组apple苹果add 增加accessible 可存取的area面积audio 音频addition 加法action 行动arithmetic 算法adjustment 调整actual 真实的argument 参量abstract 抽象ascent 提升already 已经AWT（Abstract Window Toolkit）抽象窗口工具API(Application Programming Interface）应用程序接口array apple add accessible area audio addition action arithmetic adjustment actual argument abstractB. byte 字节Boolean 布尔banana香蕉base 基础buffer缓冲器button 按钮break 中断body 身体C。
color 颜色class 类count 计数client 客户code 代码calculation 计算cell 单元circle圆capital首都catch捕获check 检查container容器component 组件command 命令cube立方，三次方char（=character)字符cancel取消case 情况choice选择click 单击center 中心compile编译clone克隆，复制continue 继续create建立D。
scoped session is already present -回复
scoped session is already present -回复Scoped Session: An In-Depth ExplanationIntroduction:In today's digital age, ensuring secure and reliable access to web applications has become crucial. One of the commonly used techniques to achieve this is by implementing a scoped session. In this article, we will explore what a scoped session is, its significance, and how it functions to enhance security and user experience. So, let's dive right in!What is a Scoped Session?A scoped session refers to a temporary and limited-duration session created for a user when they access a web application. It acts as a virtual container that holds data related to the user's session state, preferences, and other necessary information. Each user is assigned a unique session ID, which allows the server to identify and track the user's activity throughout their session.Why are Scoped Sessions Important?Scoped sessions play a vital role in ensuring the security and reliability of web applications. By creating a separate session for each user, the risk of unauthorized access and information leakage is significantly reduced. Scoped sessions restrict the scope of session data, preventing it from being accessed or manipulated by other users. These sessions also enhance the user experience by maintaining session state and preferences across multiple pages, allowing the user to seamlessly interact with the application.How Does a Scoped Session Work?1. Session Initialization:When a user accesses a web application, the server creates a unique session ID for that user. This session ID is either generated randomly or using an algorithm that ensures uniqueness. The session ID is then stored on the server and sent back to the user's browser as a cookie or parameter in the URL.2. Request Processing:As the user interacts with the web application, subsequent requests are sent to the server along with their session ID. Thisallows the server to retrieve the specific session associated with that user and process the request accordingly. The data stored within the session, such as authentication credentials or user preferences, can be accessed and utilized.3. Session Expiration:To prevent sessions from persisting indefinitely, scoped sessions are designed with an expiration mechanism. A session can have a fixed expiration time, such as after 30 minutes of inactivity, or it can be renewed with each user interaction. When a session expires, its data is typically deleted from the server, ensuring that sensitive information is not retained longer than necessary.4. Session Termination:Users can actively terminate their sessions by logging out or closing the browser. In such cases, the session ID is invalidated, and all associated session data is immediately removed from the server. This step is crucial in protecting user accounts from unauthorized access, especially when using shared or public computers.Best Practices for Implementing Scoped Sessions:1. Secure Session Management:Implement mechanisms to prevent session hijacking and unauthorized access. Use secure cookies that are not susceptible to tampering and employ encryption techniques to protect session data during transit.2. Validate User Input:Implement robust input validation to prevent injection attacks that may exploit session handling mechanisms. Ensure that session IDs cannot be manipulated through input fields.3. Secure Session Storage:Store session data securely on the server. Use encryption and access control techniques to protect the confidentiality and integrity of the stored data.4. Regular Session Expiration:Configure appropriate session timeout values to ensure sessions expire after an appropriate period of user inactivity. This helps reduce the risk of unauthorized access and ensures sensitive session data is not retained indefinitely.Conclusion:In summary, a scoped session is a crucial component of ensuring secure and uninterrupted access to web applications. By assigning a unique session ID to each user and limiting the data accessible within a session, scoped sessions enhance security and provide a seamless user experience. Developing and implementing scoped session mechanisms following best practices helps protect both users and applications from potential security threats.。
Spring技术内幕——深入解析Spring架构与设计原理(二)AOP
Spring技术内幕——深入解析Spring架构与设计原理（二）AOPAOP联盟定义的AOP体系结构把与AOP相关的概念大致分为了由高到低、从用法到实现的三个层次。
关于这个体系结构，个人的理解是这样的，从上往下，最高层是语言和开发环境，在这个环境中可以看到几个重要的概念：base可以视为待增加对象，或者说目标对象；aspect指切面，通常包含对于base的增加应用；configuration可以看成是一种编织或者说配置，通过在AOP体系中提供这个configuration配置环境，可以把base和aspect结合起来，从而完成切面向目标对象的编织实现。
对Spring平台或者说生态系统来说，AOP是Spring框架的核心功能模块之一。
AOP与IOC容器的结合用法, 为应用开发或者Spring自身功能的扩展都提供了许多方便。
Spring AOP的实现和其他特性的实现一样，十分丰盛，除了可以用法Spring本身提供的AOP实现之外，还封装了业界优秀的AOP解决计划AspectJ来让应用用法。
在这里，主要对Spring自身的AOP实现原理做一些解析；在这个AOP实现中，Spring 充分利用了IOC容器Proxy代理对象以及AOP拦截器的功能特性，通过这些对AOP基本功能的封装机制，为用户提供了AOP的实现框架。
所以，要了解这些AOP的基本实现，需要我们对Java 的Proxy机制有一些基本了解。
AOP实现的基本线索 AOP实现中，可以看到三个主要的步骤，一个是代理对象的生成，然后是拦截器的作用，然后是Aspect编织的实现。
AOP框架的丰盛，很大程度体现在这三个详细实现中，所具有的丰盛的技术挑选，以及如何实现与IOC容器的无缝结合。
究竟这也是一个十分核心的模块，需要满足不同的应用需求带来的解决计划需求。
在Spring AOP的实现原理中，我们主要举ProxyFactoryBean的实现作为例子和实现的基本线索举行分析；很大一个缘由，是由于ProxyFactoryBean是在Spring IoC环境中，创建AOP应用的最底层办法，从中，可以看到一条实现AOP的基本线索。
Net Customisation User Guide
.NET Customization User GuideAVEVA Solutions LtdDisclaimerInformation of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law. Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or entity for any actions, claims, loss or damage arising from the use or possession of any information, particulars, or errors in this publication, or any incorrect use of the product, whatsoever.CopyrightCopyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Ltd Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made.The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution.The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective licence agreements, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.First published September 2007© AVEVA Solutions Ltd, and its subsidiaries 2007AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United KingdomTrademarksAVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden.AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its subsidiaries, registered in the UK, Europe and other countries (worldwide).The copyright, trade mark rights, or other intellectual property rights in any other product, its name or logo belongs to its respective owner.AVEVA .NET CustomizationContents Page.NET Customization User GuideIntroduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1:1 About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 .NET Customization Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Common Application Framework Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2 Database Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2 Geometry Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3 Shared Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3 Utilities Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4 Graphics Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4 Sample Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4 AttributeBrowserAddin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4 ExamplesAddin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4 NetGridExample. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4 PMLNetExample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4 PMLGridExample. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:5 Reference Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:5 Compatibility with future versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:5How to Write an Addin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2:1 The IAddin Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 The WindowManager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3 Window Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3IWindow Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4 Window Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4WindowManager Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5 The StatusBar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5Addin Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6 Writing a Command Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6 Command Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:9 Resource Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:9 Configuring a Module to Load an Addin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:9 Menu and Command Bar Customization . . . . . . . . . . . . . . . . . . . . .3:1 Configuring a Module to Load a UIC File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1 Editing the UIC File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2 Selection of Active Customization File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3 The Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4Selecting a Node in the Tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5 Drag & Drop within the Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5 Node Context Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5 List of Command Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6 Selecting a Node in the List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6 Drag & Drop from the List to the Tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6 List Context Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7 Tool Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8 Sorting List via Heading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10 Property Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10 Action Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12 Resource Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13 Resource Editor Command Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:14 Using Resources for Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16 Standalone Resource Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16Database Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4:1 Data Model Definition Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 DbElementType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Constructors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 Related ENUMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 Related Pseudo Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 DbAttribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3 Constructors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3 Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3 Related ENUMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4 DbElementTypeInstance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4 DbAttributeInstance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4Element access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 DbElement Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Constructors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Identity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Element Validity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6 Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6 Basic Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6 Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7 Basic Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7 Pseudo Attributes Relating to Element Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8 Secondary Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8 Getting Attribute Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9 Basic Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9 List of Valid Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 Qualifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11 Getting an Attribute as a Formatted String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11 Database Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11 The Modification Pipeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:12 Claiming Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:13 Pseudo Attributes Relating to Claims . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:13 Set Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:14 Creating Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:14 Moving Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:15 Changing Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:15 Pseudo Attributes Relating to Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:15 Storage of Rules and Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:16 Database Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:16 Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:17 Pseudo Attributes Relating to Rules and Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:17 Comparison of Data with Earlier Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:17Filters/Iterators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19 Iterators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19 Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19Dabacon Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19 Overview of Dabacon Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19 Table Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:20 DBs, MDBs and Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:21 MDB Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:21 DB Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:22 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:23 Overview of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:23 Overview of C# Mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:23 General Capture of DB Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:24Adding Pseudo Attribute Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:24 DB/MDB Related Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:26PMLNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5:1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1 Design Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1 Using PMLNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2 Object Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3 Query Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3 Global Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4 Method Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4 Method Overloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5 Custom Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5 Private Data and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6 Instantiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7 ToString() Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7 Method Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7 Double Precision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7 Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7 Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:8 Rules for Calling .NET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:8 Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9 .NET Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9 Creating a Container. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9 Hosting .NET Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10 Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10 PMLGridExample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10 PMLNetExample. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10The AVEVA C# Grid Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6:1Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Creating a C# Addin which Contains an AVEVA Grid Control. . . . . . . . . . . . . . 6:1 Providing Access to the Addin in PDMS Design or Outfitting Design . . . . . . . 6:3 Using the AVEVA Grid Control with Different Data Sources: . . . . . . . . . . . . . . 6:4 Adding an XML Menu to the Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5 Adding an Event to the Addin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:6 Other Functionality Available within the PDMS Environment. . . . . . . . . . . . . . 6:7 Use of the C# Grid Control with PML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7 AVEVA Grid Control API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7 Input Mask Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:121Introduction1.1About this GuideThis manual is designed to give a software engineer with experience of softwaredevelopment in C# using Visual Studio guidance on the development of .NET customizationfor the AVEVA PDMS and AVEVA Marine products. Customization ArchitectureThe introduction of a customization capability using Microsoft .NET technology has openedup a whole new world of customization and is particularly relevant for the integration ofAVEVA products with other customer systems. .NET API's provided access to variousaspects of the product including Graphical User Interface, Database and Geometry.As part of AVEVA's strategy of 'continual progression' the .NET customization capability hasbeen introduced in such a way that it can be used alongside the existing PML basedcustomization. Through the use of , an enhancement to PML which allows thePML programmer to call .NET code, customization which utilizes the strengths of .NETcompiled code and PML can be achieved.Figure 1: customization ArchitectureThe above diagram illustrates the two new methods of customization using .NETtechnology. The first is via the concept of a .NET Addin and the second using .Both methods provide a mechanism whereby a .NET assembly (dll) can be dynamicallyloaded into a module at runtime.1.2.1Common Application Framework InterfacesThe Common Application Framework (CAF) is an extensible framework which provides the.NET programmer with access to various services which support both applicationdevelopment and customization. The foundations of the CAF are provided by the twointerface assemblies:•Aveva.ApplicationFramework.dll•Aveva.ApplicationFramework.Presentation.dllThese interfaces provide the following major services:Namespace: Aveva.ApplicationFramework•AddinManager: This class provides properties and methods for the management of ApplicationFramework Addins.•ServiceManager: This class defines an interface which provides a means by which the various components of the ApplicationFramework can publish their services. TheServiceManager also acts as a service provider responding to requests for services. Itcan also be used by applications and application addins to publish additional services.•SettingsManager: This class provides properties and methods for the management of application settings which are stored in settings groups which are persisted betweensessions.Namespace: Aveva.ApplicationFramework.Presentation•CommandBarManager: This provides access to the menus and commandbars of a CAF based application. It also has methods to load the definition of menus andcommandbars from User Interface customization (UIC) files.•CommandManager: This class defines an interface to provide the presentation framework client with a mechanism for the management of command objects whichcan be associated with Tools or other User interface objects. The action of invoking atool (e.g clicking a ButtonTool) will cause the execution of the associated commandobject. It is possible to associated the same command object with a number of differentuser interface objects (e.g. ButtonTool on a Menu and a LinkLabel) thereby allowing forthe centralisation of these user interface objects action within a command. Variousstate-like properties of a command (e.g. enabled/checked) would also be reflected in alluser interface objects associated with a command. For example, disabling a commandwould cause all associated user interface objects to be disabled. User interface objectsare associated with a command via a CommandExecutor derived class.•ResourceManager: This class defines an interface to provide Addins with a simplified mechanism to access localizable resources.The ResourceManager provides a numberof methods which allows an addin to then access the various types of resources (string,image, cursor, icon etc.) which resource files may contain.•WindowManager: This provides access to the main application window, the StatusBar and a collection of MDI and docked windows. It also provides the addin writer withmethods to create MDI and docked windows to host user controls.1.2.2Database InterfacesThe database related interfaces are provided by the interface assemblies:•Aveva.Pdms.Database.dll & PDMSFilters.dllThis interface has the following main classes:Namespace: Aveva.Pdms.Database•DatabaseService: The sole purpose of this class is to open a project.。
iRules经典教材!
Nathan McMahon 5/5/2008
IntroductionLeabharlann to iRulesIntro
What Can iRules Do When Should iRules Be Used TCL and iRules iControl Additional Resources 3 3 4 4 5
Common Tasks
Parsing Strings IP Addresses Data Groups Statistics Tracking Users Persistence Search and Replace Exiting Events and iRules Troubleshooting with iRules Troubleshooting iRules Optimizing iRules 32 34 39 42 44 48 51 54 57 60 62
Components of an iRule
Events Condition Action Basic Syntax Basic Commands HTTP Commands Operators Commands Continued 7 8 9 10 13 15 20 23
basic checkbox options within the LTM. Some examples include cookie encryption, header insertion via the HTTP profile, and URI load balancing via the powerful HTTP Class profile. If your requirements can be accomplished via a profile or similar built in mechanism, use it first. If your requirement cannot be met with the canned capabilities of the LTM, then it’s worth asking “without using an iRule, how could similar functionality be achieved?” A common answer is “we can have our software developers add this to the application in six months.” True. You could wait six months and expend valuable developer resources. Or instead spend thirty minutes and have the issue resolved quickly by an iRule. Other objections such as the CPU overhead are valid points and need to be evaluated on a case by case basis as will be discussed later in the Optimizing iRules section. As for being locked into the F5 BIG-IP LTM as the solution to your application networking solution, it’s worth asking the simple question, “does the LTM with the iRule solve your issues?” Every scenario is different, but in the end, it’s important to understand that by employing iRules you are not venturing into unchartered waters alone. Nearly %60 of all F5 BIG-IP LTM customers have at least one iRule in use. There is a fantastic community of tens of thousands of developers and administrators that have contributed their experiences via DevCentral to make iRules and the LTM the standard they are today in the application delivery networking space.
getting started using zemax
Getting Started Using ZEMAX®Version 1.1.6Table of Contents1 2 ABOUT THIS GUIDE ......................................................................................................................................................... 3 INSTALLING ZEMAX ......................................................................................................................................................... 4 2.1 2.2 2.3 2.4 2.5 2.6 3 INSTALLING THE KEY DRIVER ........................................................................................................................................ 4 INSTALLING ZEMAX ..................................................................................................................................................... 4 LICENSE CODES ........................................................................................................................................................... 4 NETWORK KEYS AND CLIENTS ...................................................................................................................................... 5 TROUBLESHOOTING ...................................................................................................................................................... 5 CUSTOMIZING YOUR ZEMAX INSTALLATION .................................................................................................................. 6THE ZEMAX USER INTERFACE ...................................................................................................................................... 7 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 THE LENS DATA EDITOR ............................................................................................................................................... 7 ANALYSIS W INDOWS ..................................................................................................................................................... 9 THE SYSTEM MENU .................................................................................................................................................... 10 THE NORMALIZED COORDINATE SYSTEM ..................................................................................................................... 12 DEFINING & POSITIONING SURFACES........................................................................................................................... 14 W ORKING IN THREE DIMENSIONS ................................................................................................................................ 16 MULTIPLE CONFIGURATIONS ....................................................................................................................................... 18 EXPORTING TO MECHANICAL CAD PACKAGES ............................................................................................................. 24 SUMMARY .................................................................................................................................................................. 254OPTIMIZATION ............................................................................................................................................................... 26 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 THE LENS SPECIFICATION ........................................................................................................................................... 26 ENTERING THE BASIC SYSTEM .................................................................................................................................... 26 SETTING VARIABLES ................................................................................................................................................... 31 DEFINING THE MERIT FUNCTION.................................................................................................................................. 32 OPTIMIZING THE LENS ................................................................................................................................................ 33 THE HAMMER OPTIMIZER ............................................................................................................................................ 36 ARE THERE ENOUGH FIELD POINTS?........................................................................................................................... 37 GLASS OPTIMIZATION ................................................................................................................................................. 39 TIPS FOR SUCCESSFUL OPTIMIZATION......................................................................................................................... 41Page 1 of 725NON-SEQUENTIAL RAY TRACING (EE ONLY) ............................................................................................................ 43 5.1 5.2 5.3 5.4 5.5 5.6 5.7 A SIMPLE EXAMPLE .................................................................................................................................................... 43 OBJECT POSITIONING & DEFINITION ............................................................................................................................ 46 COMBINING SEQUENTIAL AND NON-SEQUENTIAL RAY-TRACING ................................................................................... 49 TRACING RAYS AND GETTING DATA ............................................................................................................................ 50 COMPLEX OBJECT CREATION ..................................................................................................................................... 54 OPTIMIZING NON-SEQUENTIAL SYSTEMS ..................................................................................................................... 56 COLORIMETRY ........................................................................................................................................................... 596POLARIZATION, COATINGS & SCATTERING (EE ONLY) .......................................................................................... 61 6.1 6.2 6.3 6.4 6.5 6.6 POLARIZATION............................................................................................................................................................ 61 THIN-FILM COATINGS ................................................................................................................................................. 62 RAY SPLITTING........................................................................................................................................................... 66 RAY SCATTERING ....................................................................................................................................................... 66 IMPORTANCE SAMPLING ............................................................................................................................................. 68 BULK AND FLUORESCENT SCATTERING ....................................................................................................................... 697WHAT’S NEXT? .............................................................................................................................................................. 71 7.1 GETTING TECHNICAL SUPPORT ................................................................................................................................... 72ZEMAX is a registered trademark of Radiant ZEMAX, LLC.Page 2 of 721 About This GuideCongratulations on your purchase of ZEMAX! ZEMAX is the industry standard optical system design software, combining sequential lens design, analysis, optimization, tolerancing, physical optics, non-sequential optical system design, polarization, thin-film modeling and mechanical CAD Import/Export in a single, easy-to-use package. Although ZEMAX is easy to use, optical system design is a very broad area of engineering. This guide is intended to get you started using ZEMAX quickly. It is the first place to start if you are new to ZEMAX, or if you are returning to it after having not used ZEMAX for some time. You may learn something even if you have used ZEMAX for many years! We strongly recommend you take the time to work all the way through this booklet. It covers:• • • • • • • • • • • • Installing ZEMAX, and customizing its appearance and file locations to your preference. Entering a simple sequential design Understanding the normalized definitions ZEMAX uses. An overview of the multiple configurations capability. How to export components and rays to mechanical CAD packages. Optimizing a simple lens. Using some of the powerful tools ZEMAX makes available. Tilting and decentering optical components. Entering a simple non-sequential system, tracing rays, and using detectors. Colorimetry. Thin-Film Coatings. Surface, bulk and fluorescent scattering.As well as getting you started, this guide also points you to some of the other resources you can use to learn ZEMAX. In particular, the User's Manual is a detailed reference on all aspects of ZEMAX. It is supplied in PDF format and is found in ZEMAX by clicking on Help Manual. This guide refers to the various chapters and sections of the manual as it goes along, as well as to some of the many sample files distributed along with ZEMAX. Also, our web-based Knowledge Base at /kb is an indispensible resource for all ZEMAX users. It contains tutorials, worked examples and answers to many frequently-asked questions.Page 3 of 722 Installing ZEMAXTo use ZEMAX, there are two programs that must be installed on your computer. The latest versions of both can be downloaded from /updates. The two programs are:• The ZEMAX installer, which has a name like ZEMAX_YYYY_MM_DD.exe, where YYYY, MM and DD are the year, month and day of the release. Different releases of ZEMAX are identified by their release date instead of a version number. The same installer is used for both ZEMAX-SE and ZEMAX-EE, and it contains all program files, sample files and a detailed User's Manual in PDF format. The key driver installer. ZEMAX is not copy protected, and may be installed on as many machines as you wish. ZEMAX is supplied with a black USB device which allows ZEMAX to run on the machine it is plugged into, and determines whether the SE or EE feature sets are available. A multi-computer network key is also available.•You must install both programs under a user account with Administrator privileges. Only Standard User privileges are needed to use ZEMAX once installation is complete.Note: The key supplied with the ZEMAX software is worth the full purchase price of the software. If the key is lost or stolen, it will not be replaced without payment of the full purchase price. Insure the key as you would any other business or personal asset of comparable value.2.1 Installing The Key DriverThe key driver installation is straightforward. Double-click the key driver installer once you have downloaded it, and choose the ‘Complete’ installation of all program features. A dialog box will also ask for your permission to modify the firewall settings of your computer to allow remote users of your computer to run ZEMAX using Remote Desktop. If you want to authorize this, click "Yes", otherwise click "No". To change this setting, just re-run the key driver installer. Plug the key in once the key driver installation is complete, and Windows will detect the hardware key. The green LED at the end of the key will illuminate.2.2 Installing ZEMAXThe installation of ZEMAX itself is similarly straightforward. Double-click the ZEMAX installer once you have downloaded it, and step through the on-screen instructions. You may choose where on your hard drive ZEMAX is installed.2.3 License CodesWhen ZEMAX runs for the first time, it may prompt you to enter a license code. If it does, visit /updates and download the file lc.dat by right-mouse-clicking the link, choosing 'Save Target As:' and storing in your ZEMAX installation folder, overwriting the current version. If after that, you continue to see a dialog box like so:Page 4 of 72Take a screenshot of this dialog box (use Alt-Print_Screen) and paste it into an email to support@. We will promptly send you the license code or further instructions.Note: Please do not phone for a license code! License codes are complex multi-character strings and cannot be reliably given over the phone. Emailing the screenshot of the dialog box to us is the quickest, most error-free way of getting your license code.2.4 Network Keys And ClientsZEMAX can also be supplied with 5, 10, 25 and 50-user network keys. Installation is almost identical, except that the key driver and hardware key are installed on one computer (called the ‘keyserver’ machine) and ZEMAX is installed on as many other machines as you wish (the ‘client’ computers). When a client machine starts ZEMAX, it looks to the keyserver machine to see if a license is available, and if so, ZEMAX starts. Installation of the key driver on the keyserver machine is identical to the normal installation, except that you obviously MUST allow the firewall settings to be adjusted to allow network access to the key. Installation of ZEMAX on the client machines is also identical to the normal installation, except that you must tell ZEMAX where to look for the keyserver machine after installation. Navigate to whatever folder you installed ZEMAX in (by default this is /program files/ZEMAX) and locate a file called sntlconfig.xml.bak. Rename this file to sntlconfig.xml, and open it in Notepad. Edit the following line: <ContactServer> 10.0.0.1 </ContactServer> Replace the default entry 10.0.0.1 with the IP address of your keyserver machine and save the file.2.5 TroubleshootingZEMAX will run without problem in the vast majority of cases. If you do experience problems, then visit our Knowledge Base at /kb. Look at the Category ‘Installation and Troubleshooting’ for help. Make sure your key is plugged in!Page 5 of 722.6 Customizing Your ZEMAX InstallationWhen ZEMAX starts for the first time, it loads a number of default settings which you may prefer to customize to your preference. Start ZEMAX, and click on File Preferences. A multi-tab dialog box will open:This allows you to set all the ‘installation-specific’ settings.Note: Full details of all Preference settings are given in the User's Manual, chapter 4 “File Menu” or can be obtained by pressing the Help button in the dialog boxes.You should explore all these tabs, but the most important ones are: 2.6.1 The Address Tab This is shown above, and it allows you to enter information about your organization which is then printed on most graphics windows. 2.6.2 The Directories Tab This tab defines the folders that ZEMAX will use for the various file types it needs. They can be redirected wherever you wish by pressing the ? button for any path and navigating to the desired location. 2.6.3 The Editors Tab This tab allows you to adjust the appearance of the various Editors that ZEMAX uses. Adjusting the ‘Decimals’ setting affects how many decimal places ZEMAX displays in the Editor cells, but does not affect the accuracy of the data itself. All data is stored in ZEMAX as double-precision floating point numbers. Selecting "Compact" will vary the number of decimals displayed to minimize the space required to display numbers, so that trailing decimals are not displayed unless necessary. You can change the font, font size, and cell widths of all the editors.Page 6 of 723 The ZEMAX User InterfaceStart ZEMAX, and open the sample file “samples/sequential/objectives/Double Gauss 28 degrees field”. Even if you intend to use only the non-sequential mode of ZEMAX you should still follow this example, as the user interface is common to both sequential and non-sequential ray-tracing. The user interface consists of three main elements:1.The program ‘frame’ that consists of the menu strip and toolbar at the top, and a status bar at the bottom. An editor spreadsheet, in this case the Lens Data Editor. Almost all data is entered via editors, which allow the parameters that define the optical system to be easily seen, and linked together or optimized as required. Data that is rarely modified once set is entered elsewhere, as we will discuss later. For now, note that the Lens Data Editor shows a sequence of ‘Standard’ surfaces which have radius of curvature, thickness, glass type, Semi-diameter and conic constant. There are then a series of parameters, labeled 0 through 12, which are not used by this surface type, and finally a Thermal Coefficient of Expansion (TCE) column, and a coating column (for EE use only). Each surface in this lens has coating ‘AR’, which is a quarter-wave thick MgF2 coating. Analysis windows, which are the results of some calculation the program has performed. In this case, the 2-D Layout, RMS Wavefront error versus field plot, and Spot Diagram are shown.2.3.Before proceeding, click on Tools Miscellaneous Performance Test and click Run TestThis will give you a simple metric of how fast ZEMAX is on your computer. It also shows one of the best features of ZEMAX: its ability to use multiple CPUs in your computer, if available. Calculations are split up and spread over all available CPUs, and the results stitched back together again, without any user interaction.3.1 The Lens Data EditorIn sequential ray-tracing, light is traced from its source, called the ‘Object’ surface, to surface 1, then to surface 2, 3, etc. until it lands on the final ‘Image’ surface. For historical reasons this surface is always called the Image surface, even though the optical system may not form an image of the source. A laser beam expander or eyepiece for example may be afocal: this is covered later. Surfaces are inserted or deleted in the editor using the Insert or Delete keyboard keys, or via the ‘Edit’ menu which also allows individual cells or the entire spreadsheet to be copied to the clipboard. Column widths can be varied by placing the cursor in the top row, over the column separator. When the cursor turns to a ↔ symbol, click and hold the left mouse button to resize the column. Columns and rows can be hidden entirely (and unhidden) using the View menu.Page 7 of 72The ‘V’ next to some parameters means that this parameter is ‘variable’. ZEMAX is allowed to change the values in such cells in order to improve the performance. This will be discussed in more detail later.Surfaces also have a set of properties that are not directly visible in the editor. These are generally those properties that are set and then not changed. To see these properties, move the mouse over the Type cell of the chosen surface, and double click. Alternatively, click anywhere on the chosen row, and choose Edit Surface Type. A multi-tab dialog appears. From the Surface Type drop-down list you can select the type of the surface, which can be aspheric, diffraction grating, toroidal, etc.Note: See the User's Manual Chapter 11, “Surface Types” for full details of all the surface types that ZEMAX supportsSpend some time exploring each tab. The most commonly used tabs are the Type, Draw, Aperture and the Tilt/Decenter tabs. Press the Help button on each tab to read the on-line Help.Note: Chapter 5 of the User's Manual, “Editors menu”, gives full details of all the Editors and their properties.Page 8 of 723.2 Analysis WindowsAnalysis windows provide either graphical or text-based data computed from the lens as entered in the Editor. Analysis windows never change the lens data: they provide diagnostic information of the various aspects of the lens system’s performance. Analysis windows all operate with the same user interface:• • • Pressing the Update menu item, or double-clicking anywhere in the Analysis window with the left mouse button, will make the Analysis window recompute. Pressing the Text menu item will show the underlying data that is being presented graphically. The Window menu item gives you access to Copy, Export as Bitmap, Export as Text File, etc. options.A typical Analysis window is shown opposite. All Analysis windows share the same menu bar. You can zoom in on a section of interest by clicking the left mouse button, holding it down and dragging it over the region you wish to zoom in on.Note: Chapter 7 of the User's Manual, “Analysis Menu”, gives full details of all Analysis windows.Clicking the Settings menu item, or right-mouse-clicking anywhere in the Analysis window, will bring up the Settings dialog box:The layout of this box will depend on the Analysis feature used, of course. The Settings are used to control the calculation. Pressing OK will recompute the Analysis calculation. The Save, Load and Reset buttons allow default settings to be saved, recalled or reset to ‘factory’ defaults. If you save the settings of any window, those become the defaults for every file that does not have its own settings, so your preferences automatically flow through all your work. The Help button will bring up the on-line help for the window.Page 9 of 723.3 The System MenuIn addition to the surfaces of the optical system, we must also define the light that is incident on the optical system. This is done with the System menu:Or with these buttons on the button bar:3.3.1 The General Dialog Box The General dialog box contains settings that apply to the whole lens design. The most important tab is the Aperture tab, which defines how big the bundle of light coming into the lens on-axis is:In this case, we define the Entrance Pupil Diameter to be 33.33 ‘lens units’. Click on the ‘Units’ tab to see that millimeters are the defined lens units in this file. Other options arePage 10 of 72meters, centimeters, and inches. Once the lens units are defined, any length where the units are not explicitly given is in lens units. Entrance Pupil Diameter (EPD) defines the size of the on-axis bundle of light entering the lens system. In the double-Gauss sample file we are using, which is a traditional SLR-type camera lens, ZEMAX traces rays at this height through the lens and computes the size of the aperture stop surface (marked as STO in the Lens Data Editor), drawn in red opposite. The aperture stop surface is usually a ring diaphragm, so in reality the radial size of this surface defines the EPD, not the other way around. If you prefer this alternative definition, then choose the Aperture Type in the General dialog box to be ‘Float by Stop’, and then change the semi-diameter of the STO surface to say 8 mm. Double-click all the open Analysis windows to make them update to reflect this change, and notice the change in the lens apertures and performance. ZEMAX automatically computes the appropriate size of each surface so that all light passes through each surface. Another commonly used Aperture Type is ‘Object Space NA’ which is appropriate when the source is something like an optical fiber that radiates out in a defined numerical aperture. Use ‘Object Cone Angle’ if the source is defined by a source angle in degrees instead of NA. There are other definitions available for less common requirements, and several other tabs that define ‘system level’ settings for the file. Review these with the on-line Help, or see Chapter 6 of the User's Manual for full details. 3.3.2 The Field Dialog Box The term “Field” is short for field-of-view and it can be defined in three ways, one of which supports two options:• •The height of the object scene being imaged The height of the image being formed, which may be chosen to be either a real or paraxial image height The angle subtended by the object scene at the lens•Whichever you choose, it is defined by System Field, or by pressing the ‘Fie’ button:Page 11 of 723.3.3 The Wavelength Dialog Box The wavelengths dialog box, defined under System Wavelength or by pressing the ‘Wav’ button, is used to set wavelengths, weights, and the primary wavelength of the system.Wavelengths are always entered in microns. Wavelength weights can be used to define relative spectral intensity, or simply to define which wavelengths are most important in a design. The ‘primary’ wavelength is used as a default wavelength: for example, if asked to compute effective focal length, ZEMAX will compute it at the primary wavelength if no wavelength is specified.3.4 The Normalized Coordinate SystemBecause there are six ways to define system aperture, and four ways to define field of view, it is convenient to work in normalized coordinates. When performing the initial setup of your system you should choose the most appropriate aperture definition, and the most appropriate field definition, and enter the data for both of these. Subsequently, all calculations use normalized units, and you do not have to refer to the specific values entered or definitions used. 3.4.1 Normalized Field Coordinates Normalized field coordinates Hx and Hy are used throughout ZEMAX, its documentation, and in the wider optical design literature. The normalized field coordinate (0, 1), for example, is always at the top of the field of view in y, whether the field points are defined as angles or heights, and regardless of the magnitude of the field coordinates. Similarly the field coordinate (0,0) is always at the center of the field of view. For example, suppose 3 field points are defined in the (x, y) directions using object height in lens units of millimeters at (0, 0), (10, 0), and (0, 3). The field point with the maximum radial coordinate is the second field point, and the maximum radial field is therefore 10 mm. The normalized coordinate (Hx =0, Hy = 1) refers to the location on the object surface (as the field of view is defined in object height) of x= 0, y =10 mm. The normalized coordinate (Hx = 1, Hy = 0) refers to the object surface location (10, 0). You can then define any point within the field of view of the lens by its (Hx, Hy) coordinates, as long as Hx2 + Hy2 ≤ 1. This is referred to as radial field normalization, as the normalized field coordinates represent points on a unit circle. ZEMAX also supports rectangular field normalization, in which the normalized field coordinates represent points on a unit rectangle.Page 12 of 72Note: See the User's Manual, chapter 3 “Conventions and Definitions”, for full details of these conventions and all the basic definitions ZEMAX uses.3.4.2 Normalized Pupil Coordinates Similarly, normalized pupil coordinates are also used throughout ZEMAX, its documentation, and in the wider optical design literature. You define the system aperture using whatever definition is most useful, and thereafter we use the normalized pupil coordinates Px and Py to define any point within a unit circle. Therefore, the point (0,1) represents a point at the top of the bundle of rays entering the system, and (0, 0) is a point at the center of the ray bundle, no matter what the definition of system aperture is or what value it has. 3.4.3 Using the Normalized Coordinates Re-open the double Gauss 28 degree field sample file in order to undo any changes you may have made in the earlier sections. Open the Field dialog box and note that the field is defined as angle in degrees, and the maximum field point has a value of 14°. This is a half-angle, and so the full field of view is 28°.Note: ZEMAX is always clear on the definitions it uses, but these definitions are not universal in the optics industry. Always clarify with your customers what definitions they use for important system specifications to avoid costly errors!Then open the General dialog box, and under the aperture tab note that the system aperture is defined as Entrance Pupil Diameter, value 33.33. Go to the Units tab to see that the lens units are millimeters, so the EPD is 33.33 mm. Lastly, open the Wavelength dialog box and note that the design uses three wavelengths, at 0.4861, 0.5876 and 0.6563 microns respectively. The primary wavelength is set as wavelength number 2, which is 0.5876 microns. Now click on Analysis Calculations Ray Trace. This is the most fundamental calculation in ZEMAX: the tracing of a single ray. Right-mouse click on this window to bring up its Settings dialog box:Page 13 of 72。
Microsoft Dynamics 365 功能介绍说明书
D a t a f l o w sA IB u i l d e rC a n v a s A p pM o d e l -d r i v e n A p pP o r t a l A p pC l o u d f l o w sB u s i n e s s p r o c e s s f l o w sD e s k t o p f l o w sD a t a v e r s eV i r t u a l A g e n tDataverse for Teamsincluding 5 + 1 environment per 20 eligible licences, 2GB per environment.Excludes F1, A1 and ‘student use benefit’ licencesProject for the web gives access to Dataverse (plans 1, 3, 5)C a n v a s A p pM o d e l -d r i v e n A p pP o r t a l A p pC l o u d f l o w sB u s i n e s s p r o c e s s f l o w sD e s k t o p f l o w sD a t a v e r s eV i r t u a l A g e n tCreate and access unlimited canvas apps using standard connectors to extend Office 365 applications or using Dataverse for TeamsAbility to create model-driven apps in Dataverse for Teams coming soonCreate and run flows using standardconnectors to extendOffice 365 applications or within Dataverse for Teams Ability to create business process flows inDataverse for Teams coming soonCreate chatbots using standard connectors with Dataverse for Teams. Deploy to Teams only. Unlimited standard sessions within TeamsO365 and M365D365 Enterprise appsD365 standard appsAccess and customise the Dataverse environment –D365 apps must beinstalled. Create up to 15 custom tables. Full CRUD on D365 restricted tables.Access and customise the Dataverse environment –D365 apps must beinstalled. Create unlimited custom tables. Full CRUD on restricted tables.Run standalone canvas apps within the same environment as the Dynamics 365 appsRun standalone Model-driven apps within the same environment as the Dynamics 365 appsUser can access a portal app mapped to D365 environment as an authenticated internal userCreate and run flows using standard, premium and custom connectors within app context. Also includes on premise data gateway Create and run flows using standard, premium and custom connectors within app context. Also includes on premise data gateway Create and use business process flows within app context Create and use business process flows within app context Power Virtual Agent sessions (1,000/month) included with:•Chat for D365 Customer Service •Dynamics 365 Digital MessagingPer AppAccess and customise a Dataverse environment. Accrues 50MB ofdatabase capacity and 400MB of file capacity.Run up to two standalone apps (either canvas or model-driven) using standard, premium and custom connectors within one environment Run up to two standalone apps (either canvas or model-driven) within one environment. Additional canvas apps can be embedded into the model-driven app.User can access one portal app as anauthenticated internal userCreate and run flows using standard, premium and custom connectors within app context. Also includes on premise data gateway Create and use business process flows within app context Per UserAccess and customise the Dataverse environment. Accrues 250MB ofdatabase capacity and 2 GB of file capacity.Run unlimited canvas apps using standard, premium and custom connectors in your tenant and as a guest in other tenants.Run unlimited model-driven appsUser can access portal apps as an Authenticated internal userCreate and run flows using standard, premium and custom connectors within app context. Also includes on premise data gatewayCreate and use business process flows within app contextAccess and customise the Dataverse environment. Accrues 50MB ofdatabase and 250 MB of file capacity for each licence.One licenced flow can be run across the tenant using standard, premium and custom connectors. Also includes on premise data gateway. Child flows do not need to be individually licencedCreate and use business process flows Per FlowAccess and customise the Dataverse environment. Accrues 250MB ofdatabase capacity and 2 GB of file capacity for each licence.Create and run many flows using standard, premium and custom connectors. Also includes on premise data gateway Create and use business process flows Per UserP o w e r P l a t f o r m A P I R e q u e s t s2,000 API requests per user per 24-hour period10,000 API requests per user per 24-hour period (Team members 5,000)20,000 API requests per user per 24-hour period(Team members 5,000)1,000 API requests 1,000 per app pass per 24-hour period5,000 API requests per user per 24-hour period 15,000 API requests per 24-hour period 5,000 API requests per user per 24-hour period P o w e r P l a t f o r m R e q u e s t sSources: Power Platform licensing guide , Power Apps and Power Automate licensing FAQ , , Power Platform API request limits , Dynamics 365 licensing guide , Power Apps pricing , Power Automate pricing , Power Virtual Agent pricing , Dataverse capacity pricing , Power Apps Community PlanExcludes Microsoft 365 F1 licencesE.g.Dynamics 365 Sales Professional, Team members, etcE.g.Dynamics 365 Sales Enterprise, Finance, Supply Chain, etcA IB u i l d e rAccess and customise the Dataverse environment. Accrues 250MB ofdatabase and 2 GB of file capacity for each licence.Create and run many flows using standard, premium and custom connectors. Also includes on premise data gatewayCreate and use business process flowsPer user + attended RPA5,000 API requests per user per 24-hour period Run one attended bot, can be triggered from a cloud flowPower Automate unattended RPA add-on allows one unattended bot to be deployed on a local or virtualisedenvironment (US$150/bot/month)Includes 5,000 AI builder credits/monthPower Apps and Power Automate capacity add-on increases daily API requests by 10,000 (these can be stacked) at US$50/monthAccess and customise the Dataverse environment. Accrues 10GB ofdatabase, 20 GB of file and 2GB log capacity.Create and run flows using standard, premium and custom connectors within the context of the bot. Also includes on premise data gatewayCreate and use business process flows within the context of the bot30,000 API requests per user per 24-hour periodPower Virtual Agent2,000 sessions / tenant / month included. Deploy chatbots to all supported channelsPVA capacity add-on: 1,000 sessions / tenant / month at US$450/monthPVA capacity add-on: 15,000 requests/day (US$450/month )US$10/user/app/monthUS$40/user/monthUS$100/flow/month (minimum 5 flows)US$15/user/monthUS$40/user/monthUS$1,000/monthEvery tenant with a Power Apps, Power Automate or PVA license receives default capacity (PVA & Per user licenses: Database 10GB,File 20GB, Log 2GB; Per App license: 5GB, 2GB, 2GB ; Per flow license: 5GB, 2GB, 200MB). Additional Database (US$40), file (US$2) and log (US$10) capacity can be purchased 1GB increments/month.$various$various$variousPower Apps portals login capacity add-on starts at US$200/month for 100 logins (24-hour period of access) of authenticated external users. Power Apps portals page view capacity add-on provides 100,000 page views by anonymous users for US$100/monthCreated by MB Version 1 (May 2021)PVA capacity add-on: 1,000 sessions / tenant / month atUS$450/monthAI Builder capacity add-on provides 1 million monthly service credits tenant wide (must be assigned to an environment) at US$500/monthThe Ultimate Power Apps, Power Automate, Power Virtual Agents licensing matrixProduct, Feature or LimitationCreate and run flows using standardconnectors to extend Office 365 applications.No documentation found but it’s there!Personal Microsoft AccountUnknown E.g.Outlook, Hotmail accounts$Free-PremiumUsers with Windows 10 (including Home) can create localised (non-cloud triggered) attended desktop flows for free. Users with personal Microsoft accounts use OneDrive for storage.D a t a f l o w sCreate standarddataflows in Power Apps Portal and store data in Dataverse tables. Create analytical dataflows and store data in your own Azure Data Lake Storage Create standarddataflows in Power Apps Portal and store data in Dataverse tables. Create analytical dataflow and store data in your own Azure Data Lake StorageEntitlement LicenseHow the matrix works:Add-onO365 and M365D365 Enterprise appsD365 standard apps Per App Per User Per Flow Per user + attended RPAPower Virtual AgentPersonal Microsoft AccountPer UserCommunityPlanAccess and customise your own Dataverse environment. 200MB Database, 2GB filestorage. Does not count to tenant’s overall quota. Individual use only.Create and run unlimited canvas apps. Individual use only,cannot share apps. Apps can be exported to other environments Create and run unlimited model-driven apps. Individual use only,cannot share apps. Apps can be exported to other environmentsCreate your own portal App. Community Plan doesn’t allow user to access portal apps as an authenticated internal userCreate and run flows using standard, premium and custom connectors within app context. Individual use only,cannot share flows. Flows can be exported to other environmentsCreate and use business process flows within app context. Individual use only, cannot share flows. Flows can be exported to other environments750 flow runs per monthSignup for free with workor school account CommunityPlan Users with Windows 10 (including Windows 10 Home) can create localised (non-cloud triggered) attended desktop flows for free. Users without RPA licencing will use the default environment for storage.Dynamics 365 Customer Insights provides the ability to workwith DataflowsBusiness Card scanning capacity is included in:•Sales Enterprise: 10 scans/user/month•Sales Insights and Sales Premium: 200 scans/user/month Pooled at tenant level.。
Linux关闭IPv6方法：HowtodisableIPv6onLinux
Linux关闭IPv6⽅法：HowtodisableIPv6onLinuxQuestion: I notice that one of my applications is trying to establish a connection over IPv6. But since our local network is not able to route IPv6 traffic, the IPv6 connection times out, and the application falls back to IPv4, which causes unnecessary delay. As I don't have any need for IPv6 at the moment, I would like to disable IPv6 on my Linux box. What is a proper way to turn off IPv6 on Linux?IPv6 has been introduced as a replacement of IPv4, the traditional 32-bit address space used in the Internet, to solve the imminent exhaustion of available IPv4 address space. However, since IPv4 has been used by every host or device connected to the Internet, it is practically impossible to switch every one of them to IPv6 overnight. Numerous IPv4 to IPv6 transition mechanisms (e.g., dual IP stack, tunneling, proxying) have been proposed to facilitate the adoption of IPv6, and many applications are being rewritten, as we speak, to add support for IPv6. One thing for sure is that IPv4 and IPv6 will inevitably coexist for the forseeable future.Ideally the should not be visible to end users, but the mixed IPv4/IPv6 environment might sometimes cause you to encounter various hiccups originating from unintended interaction between IPv4 and IPv6. For example, you may experience timeouts from applications such as apt-get or ssh trying to unsuccessfully connecting via IPv6, DNS server accidentally dropping AAAA DNS records for IPv6, or your IPv6-capable device not compatible with your ISP's legacy IPv4 network, etc.Of course this doesn't mean that you should blindly disable IPv6 on you Linux box. With all the benefits promised by IPv6 (e.g., more efficient routing, simpler network configuration), we as a society want to fully embrace it eventually, but as part of troubleshooting process for end-user experienced hiccups, you may try turning off IPv6 to see if indeed IPv6 is a culprit.Here are a few techniques allowing you to disable IPv6 partially (e.g., for a certain network interface) or completely on Linux. These tips should be applicable to all major Linux distributions including Ubuntu, Debian, Linux Mint, CentOS, Fedora, RHEL, and Arch Linux. Check if IPv6 is Enabled on LinuxAll modern Linux distributions have IPv6 automatically enabled by default. To see IPv6 is activated on your Linux,use ifconfig or ip commands. If you see inet6 in the output of these commands, this means your Linux has IPv6 enabled.$ ifconfig$ ip addrDisable IPv6 TemporarilyIf you want to turn off IPv6 temporarily on your Linux system, you can use /proc file system. By temporarily, I mean that the change you make to disable IPv6 will not be preserved across reboots. IPv6 will be enabled back again after you reboot your Linux box.To disable IPv6 for a particular network interface, use the following command.$ sudo sh -c 'echo 1 > /proc/sys/net/ipv6/conf/<interface-name>/disable_ipv6'For example, to disable IPv6 for eth0 interface:$ sudo sh -c 'echo 1 > /proc/sys/net/ipv6/conf/eth0/disable_ipv6'To re-enable IPv6 back on eth0 interface:$ sudo sh -c 'echo 0 > /proc/sys/net/ipv6/conf/eth0/disable_ipv6'If you want to disable IPv6 system-wide for all interfaces including loopback interface, use this command:$ sudo sh -c 'echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6'Disable IPv6 Permanently across RebootsThe above method does not permanently disable IPv6 across reboots. IPv6 will be activated again once you reboot your system. If youwant to turn off IPv6 for good, there are several ways you can do it.Method OneThe first method is to apply the above /proc changes persistently in /etc/sysctl.conf file. That is, open /etc/sysctl.conf with a text editor, and add the following lines.# to disable IPv6 on all interfaces system widenet.ipv6.conf.all.disable_ipv6 = 1# to disable IPv6 on a specific interface (e.g., eth0, lo)net.ipv6.conf.lo.disable_ipv6 = 1net.ipv6.conf.eth0.disable_ipv6 = 1To activate these changes in /etc/sysctl.conf, run:$ sudo sysctl -p /etc/sysctl.confOr simply reboot.Method TwoAn alternative way to disable IPv6 permanently is to pass a necessary kernel parameter via GRUB/GRUB2 during boot time.Open /etc/default/grub with a text editor, and add ipv6.disable=1 to GRUB_CMDLINE_LINUX variable.$ sudo vi /etc/default/grubGRUB_CMDLINE_LINUX="xxxxx ipv6.disable=1"In the above, xxxxx denotes any existing kernel parameter(s). Add ipv6.disable=1 after them.Finally, don't forget to apply the modified GRUB/GRUB2 settings by running:On Debian, Ubuntu or Linux Mint:$ sudo update-grubOn Fedora, CentOS/RHEL:$ sudo grub2-mkconfig -o /boot/grub2/grub.cfgNow IPv6 will be completely disabled once you reboot your Linux system.Other Optional Steps after Disabling IPv6Here are a few optional steps you can consider after disabling IPv6. This is because while you disable IPv6 in the kernel, other programs may still try to use IPv6. In most cases, such application behaviors will not break things, but you want to disable IPv6 for them for efficiency or safety reason.1. /etc/hostsDepending on your setup, /etc/hosts may contain one or more IPv6 hosts and their addresses. Open /etc/hosts with a text editor, and comment out all lines which contain IPv6 hosts.$ sudo vi /etc/hosts# comment these IPv6 hosts# ::1 ip6-localhost ip6-loopback# fe00::0 ip6-localnet# ff00::0 ip6-mcastprefix# ff02::1 ip6-allnodes# ff02::2 ip6-allrouters2. Network ManagerIf you are using Network Manager to manage your network settings, you can disable IPv6 on Network Manager as follows. On Network Manager, open the wired connection for which you want to disable IPv6, click on IPv6 Settings tab, and choose Ignore in Method field. Save the change and exit.3. SSH serverBy default, OpenSSH server (sshd) tries to bind on both IPv4 and IPv6 addresses. To force sshd to bind only on IPv4 address, open /etc/ssh/sshd_config with a text editor, and add the following line. inet is for IPv4 only, and inet6 is for IPv6 only.$ sudo vi /etc/ssh/sshd_configAddressFamily inetAnd restart sshd server.。
C#4.0新特性
[翻译] C# 4.0新特性（白皮书）原文地址：/Project/Download/FileDownload.aspx?ProjectName= csharpfuture&DownloadId=3550（Word格式，需接受许可协议并下载。
）原著作者：Mads Torgersen, C# Language PM翻译：Anders Liu摘要：Microsoft Visual C# 3.0作为Visual Studio 2008的一部分发布以来已经快一年了。
在VS Managed Languages团队，我们一直努力创建该语言的下一个版本（没什么惊喜，就是C# 4.0），而这个文档是我们现在所看到的、计划中的语言特性的第一个公开描述。
Contents目录∙Introduction 简介∙C# 4.0∙Dynamic Lookup 动态查找∙The dynamic type dynamic类型∙Dynamic operations 动态操作∙Runtime lookup 运行时查找∙Example 示例∙Overload resolution with dynamic arguments 带有动态参数的重载解析∙The Dynamic Language Runtime 动态语言运行时∙Open issues 已知问题∙Named and Optional Arguments 命名参数和可选参数∙Optional parameters 可选参数∙Named and optional arguments 命名的和可选的实参∙Overload resolution 重载解析∙Features for COM interop COM互操作特性∙Dynamic import 动态引入∙Compiling without PIAs 无PIA的编译∙Omitting ref 省略ref∙Open issues 已知问题∙Variance 变性∙Covariance 协变性∙Contravariance 逆变性∙Limitations 限制∙COM Example COM示例∙Relationship with Visual Basic 与Visual Basic的关系∙Resources 资源Introduction简介It is now close to a year since Microsoft Visual C# 3.0 shipped as part of Vis ual Studio 2008. In the VS Managed Languages team we are hard at work o n creating the next version of the language (with the unsurprising working tit le of C# 4.0), and this document is a first public description of the planned l anguage features as we currently see them.Microsoft Visual C# 3.0作为Visual Studio 2008的一部分发布以来已经快一年了。
科技英语写作高级教程参考答案
V、练习参考答案练习1I、1、the（各项均为负。
)2、the; a （功率额定值是电阻器不会引起温度太大的上升而能安全地耗散的最大功率。
）3、an（这是均方根值伏特计。
）4、The; a（该设备的成功设计需要详细地了解性能指标。
）5、the; a; a（在氢原子的布尔模型中，一个电子绕一个质子以半径为R的圆周运转。
）6、the（电阻的单位是欧姆。
）7、an （这是一个h参数。
）8、/; /（图5－1画出了Oersted的实验。
）9、A; a; a（机器是能够传递力来完成某一确定目的的一种设备。
）10、/（水压机将在第14章加以考虑。
）11、the; the [/]（我们容易确定参数μ的值。
）12、/; the（根据式（2－1），我们得到以下的关系式。
）13、the; /（作者工作在位于阿林顿的得克萨斯大学。
）14、an（甚至当积分区间并不是无穷时，能够恰当地显示一个时函数的傅氏变换的仪器是多么重要啊！）II、1.Dr. Emmet graduated from Harvard University in 2001.2.Professor Li earned his Ph.D. degree in mechanical engineering from the Xi’anUniversity of Technology in 1988.3.Now we shall turn to the discussion of local area networks.4.The Bainbridge mass spectrometer is as important an instrument as the opticalspectrometer.5.How long a time [或How much time] is required to this experiment? The densityof a substance is its mass per unit volume.6.An increase in pressure always causes a decrease in volume.7.Fig. (2-5) shows what is expressed by Eq. (2-2).8.The unit of inductance is the henry.III、1.The UAS MA protocol employs a unique frame structure.2.Finally, a broad stepped impedance transformer is designed by this method.3.Dynamic analysis and evaluation of the security of a proactive secret sharingsystem4.The approach can be applied to the one-dimensional potential barrier with anarbitrary profile.5.We propose a numerical method based on Newton’s iterative method.练习2I、1. This circuit consists of a battery, an inductor and a capacitor.2. Compute the electric fields at points a, b, and c.3. This satellite is used for communications between the United S tates and Great Britain, France and Italy.4. We assume that the antenna is vertical and that its loss is zero.5. Chapters 6, 7, and 8 deal with transmission lines.II、1. Its error is six parts in 1012.2. This computer stores four times more information than that one (does).3. The demand for this kind of equipment in the near future will be 20 times what it is.4. The voltage across this component is a few tenths of a volt.5. Now its internal pressure is one sixteenth what it was.III、1. This object is over five times heavier than that one is.2. Unless otherwise stated, it is assumed that silicon transistors are used and that I CB Ocan be neglected.3. This circuit has the advantages of simple structure and easy adjustment.4. Figs. 1, 2, and 3 show this process in detail.5. For further information, consult references [3, 5, 9].练习3I、1. This new type of computer has many advantages over the general type.2. It is not difficult to solve this differential equation for the unknown quantity.3. Of these five new chapters, the first one deals with the basic principles of negative feedback.4. At this point/time, current differs in phase from voltage by 90o.5. By analyzing [By the analysis of] the parameters of the instrument, we can understand its performance.6. We will find out its average velocity over this distance.7. The science of electronics is too important in the world today.8. They solved this problem with great difficulty.II、1. For x＞1, there is no solution to this equation [this equation has no solution].2. Upon [On] substituting [substitution of] these values into [in] theequation, we obtained the following expression..3. This circuit is similar in operation to that of Fig. 1-10.4. This computer is very good in performance.5. These waves travel only in one direction.III、1. This paper presents a new method for the recognition of radar target s.2. The influence of the moving state of the target on the tracking accuracy of the EKF is great.3. Another comsat was launched on the morning of the 8th of October.4. V oltage is measured in volt s.5. They will leave for Beijing to attend an international conference on mobile communication.6. Unless otherwise stated, it is assumed that silicon transistors are used and that I CBO can be neglected.7.练习4I、1. The force acts perpendicular to the surface of the table.2. The three coefficients here remains to be determined.3. The two equations below will be often (frequently) used in later chapters/in thechapters which follow.4. Here we use two metal balls 10 cm apart.5. The output remains/stays constant/unchanged/fixed/unaltered/the same.6. All the textbooks available discuss this problem.7. Accurate in operation and high in speed, computers have found wide applications.8. The answer to this problem looks correct.9. Two parallel wires a distance (of)δapart carry the current i.10. The problem now is how to measure the voltage across this component.11. These data will be sent to the computing center 2 kilometers away.12. Upon rearranging the equation above, we have [get, obtain] the following expression.13. These charges can interact with other charges present.14. Forces can be transmitted without contact, contrary to the common belief.15. This coefficient is typically 0.35.II、1. In this case, the input does not fall; nor [neither] does the output. […; the outputdoes not fall, either.]2. The resistance of a conductor depends not only on the material of which theconductor is made, but also on the size and temperature of the conductor.3. These scientists are very interested in this topic.4. This parameter can hardly be measured.5. In this laboratory, this instrument is more expensive than any other one/ any one else.6. The features of this device are small size and light weight.练习5I、1. This equation can be solved in either of the following two ways/the two ways which follow.2. This baseball will soon come to rest because of its interaction with the ground.3. Our choice of this coefficient as 1 is correct.4. From its definition as the ratio of a force to a length, we can see that k has the same unit as work (does).5. Our analysis of the machine is of great significance.6. This facilitates their use in circuit analysis.II、1. This police car is equipped with a receiver the size of a matchbox.2. Wires one hundredth the diameter of a silk thread are used to connect these components.3. W e must water cool these equipments/devices.4. In the past, telephone calls were operator connected.5. AC can be changed/turned/converted/transformed/translated into/to DC, a process called/known as/referred to as rectification.6. A magnet attracts iron materials, a familiar phenomenon.7. Computers are capable of processing information, a process that previously could be accomplished only inside our heads.8. An instrument for measuring current, voltage, and resistance, the multimeter is widely used in electrical engineering.III、1. Secs. 1.1 and 1.2 will discuss several other problems.2. Problems are listed/given on pp. 1-5.3. In the equations above, all h’s are the hybrid parameters.4. The mass of the standard pound is equal to 0.4535924277 kilogram s.5. All a’s and b’s in Eq. (5-1) are related to the impedance R o.6. W e must take the effect of temperature on [upon] semiconductors into account.7. In this case, the variation of output with input is very small.8. This curve shows the dependence of distance on/upon speed.IV、1. None of them can solve this special type of differential equation.2. They do not know whether this material can stand so large a force or not.3. There are M polygons altogether, each of which has N vertexes.4. These two engineers are busy (in) designing a new kind of software.5. Iron is almost as good a conductor as aluminum.练习6I、1. This image, it will be noticed, is a real image.2. This technical problem, we hope, will be solved soon.3. 210 is approximately 1000, a fact that we think is very useful in the study of digital electronics.4. A resistor of say 100 ohms should be used here.II、1. None of those textbooks have/has mentioned this point.2. All of these x values cannot satisfy the equation.3. Neither of the two conditions is satisfied here.4. In the preceding/previous chapter, we discussed all kinds of force.5. This paper describes a new method for designing aircraft.6. By the end of the last century, the company had manufactured 5 000radars.7. Since 2008, this research institute has been developing a special kind of robot.III、1. In Section 1-2, the concept of force was introduced.2. As early as the 1940s, it was found that semiconductors are very useful.3. This result can also be arrived at in another way.4. At that time no use was made of this phenomenon/…, thisphenomenon was made no use of.5. This point will be dealt with in the next section.IV、1. This computer works much better than that one (does)/This computer is much better in performance than that one (is)..2. This computer requires many more components that that one (does).3. The distance of the moon from the earth is as great as 240 000 miles.4. The greater the resistance, the longer time it takes for the capacitor to reach its maximum voltage/…, the longer time is required for the capacitor to reach its maximum voltage.)5. The current as small as 0.1 A cannot produce enough heat.V、1. It is easy for us to determine the weight of the body. 或：We can determine the weight of the body easily.2. The two engineers are busy (in) designing a new type of computer.3. We find this concept very difficult to explain.4. None of these windows can withstand so large a force.5. Work equals [is equal to] force multiplied by/times distance.6. The results obtained agree with the experimental values. [… are in agreement with the experimental values.]练习7I、1. It will take a few months to design this kind of aircraft with the help of a computer.2. It is left as a problem to [for] the reader to show that this expression holds.3. The program to be executed is stored in this unit.4. This valley acts as the foundation on which to build the dam.5. In this laboratory there are many kinds of instrument for students to choose from.6. Let t0 equal/be equal to zero.7. The farther away the target (is), the longer time it takes for the echo to return.8. For the series to converge, x must be less than 1.9. We find this concept very difficult to understand.10. This method makes it much easier to detect targets.11. This factor will affect the ability of a computer to store information.12. We have to find out how large to make r so as for the series to converge.13. This is a pen to draw pictures with.14. Elasticity is the tendency of a body to return to its original condition after being deformed.15. Ordinary matter is said to be electrically neutral.16.This property makes it possible for metals to be made into any shape.17. This table is unfit for a student to do experiments on.18. Now we consider what path of integration to take.II、1. The sine law of the variation of light intensity with the cylinder diameter has been emphasized.2. Not only do temperature and light affect the conductivity, but the addition of impurities to semiconductors also makes it change greatly.3. V arious satellites are frequently launched to obtain information about/on space.4. Our semiconductor industry came into being at the end of the 1950s.5. My colleagues and I would like to express our thanks to Professor W. Smith for his great help.练习8I、1. The amplifier amplifies the received signals.2. Moving molecules have kinetic energy.5. Fig. 1 – 3 shows the photo of a freely falling body.3. Speed equals distance divided by time.4. V oltage equals/is equal to current multiplied by resistance.5. The resistance of air increases with the increased/increasing/an increase in speed.6. A transformer is a device consisting of two or more coils wound on/round an iron core.7. It is necessary to find out the current flowing through this component.8. This book, properly used, will be of great help to the reader.9. Flowing through a circuit, the current will lose part of its energy.10. Given/Knowing time and speed, we/one can find out distance.11. Having studied this chapter, the student will understand/will have understood the principle of a computer.12. The speed of light being extremely great, we cannot measure it by ordinary methods.13. Several comsats were launched, all of them (being) high-altitude satellites.14. Called “the mother of all networks,”the Internet is a widely used international network.15. This force can be resolved into two components, one (being) horizontal and the other vertical.II、1.Let us construct/draw a circle with the origin as the center and of radius R.2.This parameter should be measured with E grounded.3. With no resistance in the circuit,the current will increase indefinitely.4. With this in view, we have written this book.5. This paper introduces a new design method/technique, with emphasis on its principle. III、1.Let us consider designing a computer.2.We refer to these components as being passive.3.This involves taking the Fourier transform.4.On/Upon rearranging the above equations, we obtain the following set ofequations.5.In using this equation, it does not matter which plane is considered as 1.IV、1. Given/Knowing resistance and current, one/we can determine/calculate voltage.2. The price of this instrument is high.3. A robot is a special kind of electronic device.4. The current starts flowing at the very moment we close the circuit.5. They have been designing a new type of computer these six months.练习9I、1. The problem was not solved until a completely different method was introduced.2. Nearly 100 years passed before the existence/presence of subatomic particles was confirmed by experiment/experimentally.3. The year this device was invented, World War II broke out.4. Small as they are, atoms are made up of still smaller particles.5. These two resistors should be selected/chosen so that the transistor can operate normally.6. The body is in such a state that it can do work.II、1. The relation that voltage is the product of current and resistance applies to all the dc circuits.2. The discovery that magnetism can produce current is extremely important in the field of electricity.3. An equation is an algebraic statement that two algebraic expressions are equal.4. There is evidence that no life exists on the moon.5. The question now arises whether the algorithm is of practical use.6. In this case there is no guarantee that the series is convergent.7. There is a growing/increasing awareness that these techniques/methods are very useful.8. One of/Among the most noteworthy achievements at that time was the realization that light consists of electromagnetic waves.9. This is due to/is caused by/results from the fact that there are many free electrons in conductors.10. Besides/In addition to the fact that the properties of the material should be included in the analytical model, we must take other factors into account.III、1.These features make it difficult for electronic counter-measure systemsto intercept, analyze and jam this kind of signal.2. The existence of and the ability to control these phenomena make those devicespossible.3. The variation of/in the number of the filter’s teeth has a greater effect on the performance of its passband than the variation of/in its dimensions.4. Scalar detection will result in the loss of some phase information.5. Fig. 6 shows the schematic diagram of measuring scatter parameters by the natural parameter transformation method.练习10I、1. Now it remains to be determined when the series converges.2. It is clear from Dubamel’s Theorem that this limit exists.3. It follows from Maxwell’s hypothesis that whenever there is a change in an electric field, a magnetic field is produced.4. It does not matter whether the magnet is moved in this case.5. Temperature determines in what direction the transfer of heat will take place.6. It is now a well-known fact that all matter consists of tiny particles.II、1. What a generator does is (to) change mechanical energy into electrical energy.2. What this chapter describes/What is described in this chapter is of great importance.3. Matter is what can occupy space.4. What we have discovered in this experiment is the entirely new realm of electrical phenomenon.5. This direction is opposite to what has been assumed.6. Magnitude, direction, and place of application are what we call the three elements of a force.7. These numbers constitute what is known as the real number system.8. In what follows, we shall acquaint ourselves with some basic concepts.III、1. An x-band wave-guide test system is shown in Fig.7. [或：Fig. 7 shows …].2. This method lowers the requirement for the hardware of a sample network.3. On the basis of the above analysis of the decomposition of the polynomial, a novel configuration results. [或：The above analysis of the decomposition of the polynomial results in a novel configuration.]4. Finally, an analysis of packet loss probability is made by computer simulation.5. The sparse ratio of the resulting impedance matrix is as high as 40%.练习11I、1. The meter (that/which) we use to measure the voltage across a resistor is called a voltmeter.2. Computers are the most efficient assistants (that) man has ever had.3. Now this disease is no longer the serious problem (that) it once was.4. Radar can measure the time (that) it takes for the radio echo to return.5. We must calculate the distance (that/through which) the body is lifted.6. The direction (that/in which) a body moves is also very important.7. The number of times (that/by which) this particle vibrates per/a second is called/termed/named/known as/spoken of as/referred to as frequency.8. We equate these two ratios, from which the simplest formula follows/results.9. It is necessary to determine the time when/that/at which the y-component has decreased to zero.10.. The curve the y-coordinate of each point on which is zero is just the x-axis.II、1. The point at which the circle cuts the axis of reals is where α= ω.2. The force of gravity means the force with which the earth attracts a body.3. The surface of a picture tube upon which the electrons produce the picture is called the screen.4. The author would like to express thanks to the editors of the series of which this book is a part/to which this book belongs.5. This is a parallelogram of which the two given vectors are/form sides.6. The pressure is equal to the total force divided by the area over which it is exerted.7. The two elements of which water consists are hydrogen and oxygen.8. This depends on the efficiency with which electrons are produced.9. These two laws are the foundation on which all other laws are built.10. The temperature at which water freezes is generally 0o C.III、1. As the title indicates, this chapter will discuss nonlinear equations.2. As the name shows, a fluid is a substance which flows readily.3. This single force produces the same effect as is produced by those forces together.4. Now we are able to solve such differential equations as occur in physics.5. This function can be accomplished by using the full adder as was described in the previous section.6. These concepts enable us to understand a wide range of phenomena in electrostatics, or “static electricity,” as it is called.7. This current is, as predicted, very small,8. First let us consider the simplest circuit as shown on page 2.IV、1. This is a slightly higher value than we predicted.2. This reactor can produce more fuel than it consumes.3. Let us consider the case when the torque is zero.4. We must determine the values of currents and voltages after the switch closes.5. During the ten years since this book was first published, significant changes have taken place/have been seen in metal-making.V、1. Even in this case these protocols can provide a limited number of users with the acceptable quality of voice service.2. This paper presents a method for an 8098 microcontroller to series-communicate witha 386 personal computer.3. The effect of equalizer parameters on equalization performance is analyzed in detail.[A detailed analysis is made of the effect of equalization parameters on equalization performance.]4. Each receiver channel in Fig. 1 contains an RF amplifier, a mixer, an IF amplifier, an A/D converter, etc.（注意：句尾的句号与缩略词“etc.”的黑点重合在一起了）5. The larger the abnormal extent (is), the larger is the residual mismatch, with the curve going up.练习12I、1. be grounded;2. be carried;3. be raised;4. be;5. not try;6. be; be satisfied;7. be;8. be; was; have; 10. were concentrated; 11. had been; 12. were moving; 13. is going to rain; 14. be; 15. leakII、1. Should anything abnormal happen, switch/turn off the power supply at once/immediately.2. Had electronic computers not been used, it would have taken them a long time to solve this problem.3. It is very important that all solutions (should) be checked in the original equation.4. It is suggested that this design (should) be modified at once.5. Without semiconductors, satellite communications would be impossible.6. We could also have used Theorem (6) to derive the result.7. The requirement that energy (should) be conserved must be satisfied.8. Everything here, be it a component or a device, is home-made.III、1. It was this scientist who/that discovered this phenomenon a century ago.2. Tungsten is the very metal used in electric lamps.3. The speed with which sound waves move through a medium does depend on the properties of the medium.4. It is not clear yet under what conditions it is that this formula can be used.5. This property we call inertia.IV、1. The author is engaged in the teaching of and the research on computer vision, and image processing and recognition.2. Let P and Q be two Boolean permutations of the same order, and then their composition is a new Boolean permutation.3. Three algorithms are presented, which can remarkably reduce the time to raise the pen, thus raising the drawing efficiency.4. What this paper describes is of great interest to communications engineers.5. The minimum entropy technique for estimating the Doppler frequency rate is presented, which has the advantages over the classical techniques of high accuracy and a small amount of computation.练习13II、1. By electromagnetic force is meant the potential difference across the battery when there is no flow of current.2. In the table below/which follows are listed various parameters of familiar computers.3. An element cannot be decomposed, nor can it be broken up by chemical methods.4. Only when x = 8, does this equation hold/apply.5. Of particular importance/Especially important are the two concepts which follow.6. Such a set we call the mathematical system.7. Rarely does one know this function with precision.8. This interrelationship between electric and magnetic fields makes possible such things as the electromagnet and the electric motor.9. Not until 1818 was the diffraction of light interpreted/explained.10. By no means do electrons move from the positive terminal to the negative terminal ina wire.II、1. The effect of air resistance is discussed in Chapter 15, and the decrease in acceleration with altitude in Chapter 17.2. It is necessary to determine the charge on and the voltage across this capacitor.3. In this case, no standard is needed, but only a numerical convention.4. This voltage is greater than or equal to 0.4 volt.5. The cathode, when heated, emits electrons.6. Every body, whether accelerated or not, is considered (to be) in equilibrium.7. If necessary, the wire will be covered with some insulation.8. The transistor has its materials arranged p-n-p, hence the name pnp transistor.III、1. An initial analysis is made of the performance of the device.2. The magnetic field is the space around a magnet occupied by the magnetic lines of force.3. This leads to the battery voltage in the model of 500 mV.4. This graph shows the variation with frequency of the resistance of the resistor.5. This is responsible for the direct return to the atmosphere of more than half the water that falls on the land.6. The question now arises how these unknowns can be determined.7. It is necessary to determine the effect on the device of changing the ambient temperature.8. The assumption has been made that the pressure always remains constant during the test.IV、1. The simulation results show that both the schemes are easy to implement.2. The model and algorithm proposed in this paper are to a certain degree/extent superior in performance to the conventional BP algorithm.3. A new technique for estimating the frequency deviation is proposed which gives a high accuracy and requires a small amount of computation.4. Improvement of the accuracy of range alignment in ISAR imaging (by) using the super resolution technique5. Research on and the realization of DTMF in a Cipher Coder6. Analysis of the ability of a quartz flexibility accelerometer to resist bad environment。
Apache Seata XA Mode
PrerequisitesDatabases that support XA transaction.Java applications that access database via JDBC.Overall MechanismIn the distributed transaction framework defined by Seata, XA mode is a transaction mode that manages branch transactions using the XA protocol mechanism, leveraging transaction resources such as databases and message services with XA protocol support.Execution Phase:Rollbackable: Business SQL operations are placed in XA branches, and the XAprotocol support ensures rollbackability.Persistent: After XA branches are completed, XA prepare is executed, and again, XA protocol support ensures persistence (i.e., no unexpected situations willprevent rollback).Completion Phase:Branch Commit: Execute XA branch commit.Branch Rollback: Execute XA branch rollback.Working Mechanism1. Overall Operation MechanismXA mode runs within the transaction framework defined by Seata:Execution Phase (E xecute):XA start/XA end/XA prepare + SQL + Register BranchCompletion Phase (F inish):XA commit/XA rollback2. Data Source ProxyXA mode requires XAConnection.There are two ways to obtain XAConnection:Option 1: Developers are required to configure XADataSource.Option 2: Create it based on the developer's regular DataSource.The first method adds cognitive burden to developers, as they need to learn and use XADataSource specifically for XA mode, which contradicts the design goal of transparent XA programming.The second method is more developer-friendly. Like the AT mode, developers do not need to worry about any XA-related issues. They can maintain the local programming model.We prioritize designing and implementing the second method: DataSource proxy creates the corresponding XAConnection based on the regular JDBC connection obtained from the regular data source.Compared to the data source proxy mechanism in the AT mode, it looks like this:However, the second method also has its limitations: it cannot guarantee compatibility correctness.In fact, this method is what database drivers should do. The implementation mechanisms of database drivers from different vendors and versions are vendor-specific. We can only ensure correctness on well-tested driver programs. Differences in the versions of driver programs used by developers may lead to the failure of the mechanism.This is particularly evident with Oracle. See the Druid issue:Taking all factors into consideration, the data source proxy design for XA mode needs to support the first method: proxy based on XADataSource.Compared to the data source proxy mechanism in the AT mode, it looks like this:3. Branch RegistrationXA start requires an Xid parameter.This parameter needs to be associated with the Seata global transaction's XID and BranchId so that the TC can drive the XA branch's commit or rollback.Currently, Seata's BranchId is generated uniformly during branch registration. Therefore, the timing of XA mode branch registration needs to be before XA start.A possible optimization in the future is:Delay branch registration as much as possible. Similar to the AT mode, we register the branch just before local transaction submission to avoid registering meaningless branches in case of branch execution failure.This optimization direction requires changes to the BranchId generation mechanism. BranchId should not be generated through branch registration but should be generated separately and then used to register the branch.How to use XA ModeFrom a programming model perspective, XA mode is identical to AT mode.You can refer to Seata's official sample:seata-xaIn the sample, the upper-level programming model is the same as the AT mode. You only need to modify the data source proxy to switch between XA mode and AT mode:@Bean("dataSource")public DataSource dataSource(DruidDataSource druidDataSource) {// DataSourceProxy for AT mode// return new DataSourceProxy(druidDataSource);// DataSourceProxyXA for XA modereturn new DataSourceProxyXA(druidDataSource);}。
[开源].NetormFreeSql1.5.0最新版本（番号：好久不见）
![[开源].NetormFreeSql1.5.0最新版本（番号：好久不见）](https://img.taocdn.com/s3/m/172f3b1af68a6529647d27284b73f242336c31b4.png)
[开源].NetormFreeSql1.5.0最新版本（番号：好久不见）废话开头这篇⽂章是我有史以来编辑最长时间的，历时 4⼩时原本我可以利⽤这 4⼩时编写⼀堆胶⽔代码，真⼼希望善良的您点个赞，谢谢了！！很久很久没有写⽂章了，上⼀次还是在元旦发布 1.0 版本的时候，今年版本规划是每⽉底发布⼩版本（年底发布 2.0），全年的开源⼯作主要是收集⽤户需求增加功能，完善测试，修复 bug。
FreeSql 1.0 -> 1.5 相隔半年有哪些新功能？只能说每个功能都能让我兴奋，并且能感受到使⽤者也⼀样兴奋（妄想症）。
迫不及待的⼈会问，这更新速度也太快了吧，升级会不会有问题？不了解版本的更新⽇志，直接升级不是好的习惯，建议关注我们的更新⽇志（github 上有专门的⽂档）；我们的版本开发原则：在尽量保证兼容的情况下，增加新功能，砍掉少量不合理的功能；我们的单元测试数量：4000+，这是我们引以⾃豪，发布版本的保障；⼊戏准备QQ群：4336577(已满)、8578575(在线)、52508226(在线)为什么要重复造轮⼦？FreeSql 主要优势在于易⽤性上，基本是开箱即⽤，在不同数据库之间切换兼容性⽐较好。
作者花了⼤量的时间精⼒在这个项⽬，肯请您花半⼩时了解下项⽬，谢谢。
FreeSql 整体的功能特性如下：⽀持 CodeFirst 对⽐结构变化迁移；⽀持 DbFirst 从数据库导⼊实体类；⽀持丰富的表达式函数，⾃定义解析；⽀持批量添加、批量更新、BulkCopy；⽀持导航属性，贪婪加载、延时加载、级联保存；⽀持读写分离、分表分库，租户设计；⽀持 MySql/SqlServer/PostgreSQL/Oracle/Sqlite/达梦/翰⾼/MsAccess；1.0 -> 1.5 更新的重要功能如下：⼀、UnitOfWorkManager ⼯作单元管理器，可实现 Spring 事务设计；⼆、IFreeSql.InsertOrUpdate 实现批量保存，执⾏时根据数据库⾃动适配执⾏ merge into 或者 on duplicate key update；三、ISelect.WhereDynamicFilter ⽅法实现动态过滤条件（与前端交互）；四、⾃动适配表达式解析 yyyyMMdd 常⽤ c# ⽇期格式化；五、IUpdate.SetSourceIgnore ⽅法实现忽略属性值为 null 的字段；六、FreeSql.Provider.Dameng 基于 DmProvider 访问达梦数据库；七、⾃动识别 EFCore 常⽤的实体特性，FreeSql.DbContext 拥有和 EFCore ⾼相似度的语法，并且⽀持 90% 相似的 FluentApi；⼋、ISelect.ToTreeList 扩展⽅法查询数据，把配置⽗⼦导航属性的实体加⼯为树型 List；九、BulkCopy 相关⽅法提升⼤批量数据插⼊性能；⼗、Sqlite :memrory: 内存模式；FreeSql 使⽤⾮常简单，只需要定义⼀个 IFreeSql 对象即可：static IFreeSql fsql = new FreeSql.FreeSqlBuilder().UseConnectionString(FreeSql.DataType.MySql, connectionString).UseAutoSyncStructure(true) //⾃动同步实体结构到数据库.Build(); //请务必定义成 Singleton 单例模式UnitOfWorkManager ⼯作单元管理器public class SongService{BaseRepository<Song> _repo;public SongService(BaseRepository<Song> repo){_repo = repo;}[Transactional]public virtual void Test1(){_repo.Insert(new Song { Title = "卡农1" }); //事务1this.Test2();}[Transactional(Propagation = Propagation.Nested)] //嵌套事务，新的（不使⽤ Test1 的事务）public virtual void Test2(){_repo.Insert(new Song { Title = "卡农2" });}}BaseRepository 是 FreeSql.BaseRepository 包实现的通⽤仓储类，实际项⽬中可以继承它再使⽤。
ESICM循环休克与血流动力学监测
未分级
treatment of the shock etiology, with frequent reassessment of response
最佳临床 实践
对于初始治疗无反应和（或）需要输注升压药物的休克患者，我们推荐留置动脉和中心静脉导管。 17. We recommend arterial and central venous catheter insertion in shock not responsive to initial therapy and/or
定义
休克可以导致细胞缺氧，并伴有血乳酸升高。
2
As a result, there is cellular dysoxia, associated with increased blood lactate levels
未分级
事实陈述
休克可以表现为四种类型：其中三种为低血流状态（低血容量性，心源性，梗阻性），另一种为高动力状态
未分级
variables (including signs of hypoperfusion, urine output and mental status) in patients with a history and
clinical findings suggestive of shock
7.
我们推荐不要根据单一的指标（诊断和/或治疗休克）。 We recommend not to use a single variable (for the diagnosis and/or management of shock
推荐级别1; 证据级 别低 (C)
推荐意见
12.
休克状态下乳酸水平通常> 2 mEq/L (mmol/L)。 Lactate levels are typically >2 mEq/L (or mmol/L) in shock states
GE Healthcare Senographe Pristina 用户手册说明书
GE HealthcareWomen’s HealthcareSenographePristinaGE imagination at workThe Senographe* Pristina is a full field digital mammography system designed to offer an extensive breast care solution with screening and diagnostic capabilities, focused on an ergonomic design for the technologist and patient comfort. Senographe Pristina features a 24 x 29 cm detector, designed to offer full breast coverage in a single image. Smaller breasts can also be imaged in any view with paddles that can slide to both sides of the detector.The Senographe Pristina does not require daily calibration. Ergonomics for technologists•Re-imagined user interface• Park Positioning during patient positioning• One touch access to preset rotation for positioning• Variable speed motorized gantry movements• Sliding compression paddles can move to the side of the detector for compressionErgonomics and design for patient comfort•Designed for Patient comfort•Wheelchair access, MITA compliant•Thinner Bucky than previous platform•Rounded edges detector for patient comfortImage quality• Automatic Optimization of Parameters (AOP), selects all exposure parameters based on breast radiological properties • Three AOP modes + 1 Automatic mode for implants• eContrast is an image processing feature that makes automatic adjustments of brightness and contrast• DQE at IEC 62220-2-3 equivalent spectrum, at 75µGy: 70% (+/-3) at 0.5lp/mm and 64% (+/-3) at 2lp/mm Smooth digital workflow connectivity• Automated Quality Control• Integrated Repeat and Reject AnalysisTechnical SpecificationsDetector• Detector ready to use right after system boot• Detector size: 24 x 29 cm• Pixel size (pitch): 100 μm• Acquisition dynamic range: 14 bits• Bucky front cover thickness: 49mm• Optimized room for positioning due to the bucky depth: 470mm • Image size:– LFOV image size - approx. 13 MB per image– Regular image size - approx. 9 MB per image• Patented needle structure CsI scintillator, single piece construction• Breast support with rounded edge• Air coolingTube technology• X-Ray tube type: Artemis• Anode target materials - Dual track: Molybdenum (Mo) enriched with Vanadium, and Rhodium (Rh)• Four focal spots: 0.1 and 0.3 IEC on each target• Target angle: 0 degree• Maximal high voltage: 49 kV• Tube current:– Molybdenum target:• 100 mA from 25 to 30 kV on large focal spot• 40 mA from 25 to 30 kV on small focal spot– Rhodium target:• 62 mA from 25 to 30 kV on large focal spot• 35 mA from 25 to 30 kV on small focal spot• Anode size (tracks diameter): 100 mm• Anode heat storage capacity: 250kJ (340 kHU)• Anode maximum dissipation: 500 W (40 kHU/min)• Max casing con tinuous dissipation:150 W (12 kHU/min) at 40 °C• Permanent filtration: 0.69 mm Beryllium• Weight: 7 kg• X-ray tube assembly: self-encased X-ray tube, oil-free, lead-free, air-cooled head• Tube protection: software monitoring of tube loadGrid/breast support•Universal grid compatible with 2D Conventional Mammography and DBT•Ergonomic breast support designed for patient comfort and cleanability• Motorized lock of the grid and breast support• Breast support material: carbon fiber composite• Optimized grid motion ensuring no grid structure visible in the image• Detector to breast support edge-to-edge distance ≤ 5 mm• It is always possible for the technologist to takecompression control even if the patient has started self-compression• PAC is inhibited during acquisition, the patient cannot interfere with the examinationPositioner• Isocentric arm with motorized rotation and vertical movement• Source to image receptor distance: 660 mm• Floor to image receptor distance: from 65 cm to 150 cm • Rotation angle: -180/+180 degrees• Ergonomic hand -rest: one at each side of the tube arm and two additional behindSafety features• Gantry motions locked when compression force appliedUser interface• Four sets of single speed switches for rotation , angulation and lift movements, with an accelerating speed profile• Four sets of preset position switches for positioning in CC and MLO• Automatic sto p at +/- 90 degrees for lateral positions • Collimation buttons on the tube head for field of view size and location• Parameters display– Tube arm support rotation angle– Compressed breast thickness (in mm) – Compression force (in daN)• Ergonomic control console– Controls exposure– Provides information on system status– Gives access to advanced parameters for system set-up• Patented automatic view names marking based on breast laterality• View name can be edited while the exam is performedAcquisition workstation• Time to display processed image (average): 10 seconds • Time between exposures (typical): 12 seconds• Dose calculated and displayed on the image after every exposure (Entrance Skin Dose and Average Glandular Dose) • Quad core Intel i5 workstation:– Memory: 32GB– Hard disk: 1 internal 250GB disk for the system – Hard disk: 1TB for image storage – Ports: 4 Gigabit Ethernet port – DVI Display and port connector• 2 types of display available – 1MP LCD Monitor• 48 cm (19”) medical grade • 1280 x 1024 pixels (landscape) • High luminance - up to 300 Cd/m2 • Contrast ratio: 2000:1• Viewing angle: 170 degrees• Mounted on a rotating arm for in -room accessAutomatic exposureAutomatic Optimization of Parameters (AOP) Fully automatic mode• AOP is an automatic exposure system that selects all exposure parameters based on radiological density of the breast: - track (Mo or Rh) - filter (Mo or Ag) - kV - mAs• The system identifies the densest part of the breast to select the appropriate exposure parameters • Three AOP modes are available:– "Standard + ”: dose to patient comparable to screen/film Mammography– “Dose -”: priority is given to dose reduction– “Standard”: balances low noise and dose reduction • Automatic acquisition mode for implants Manual mode• Manual selection of all parameters: track, filter, kV and mAsCollimator• Filters: Molybdenum: 0.030 mm; Silver: 0.030 mm • Field of View (FOV) in detector plane, in cm:– For standard contact views: 24 x 29 maximum FOV or 19 x 23 regular FOV, automatic adjustment depending on paddle used, breast support and gantry rotation angle• Field of View (FOV) selection: automatic and manual• FOV size: selected automatically based on the paddle or geometric magnification platform used, can be modified manually by using the collimation size switch on the tube head • FOV location (left, right, center): selected automatically based on the tube arm angle, can be modified manually by using the collimation position switch on the tube head • Compression and exposure are prevented if the FOV and compression paddle sizes or locations are not consistent • Light centering device: a light automatically switches on when a preset position is reached, at compression start or at paddle insertion; can be turned on with the collimation switches buttons located on the tube head or on the acquisition consoleCompression• Compression modes:– Motor driven compression up to 20 daN – Manual compression up to 27 daN• Dual foot-pedals for column height and compression adjustments• User defined motorized compression force limit: 4 to 20 daN • Min force for AOP: 3 daN• Compression speed: 3 speed levels• Selectable automatic decompression after exposure, to minimize patient time under compressionPatient Assisted Compression (PAC)*Commercialized as Pristina Dueta in some countries• Wireless and ergonomic -designed device that allows the patient to continue the compression after the technologist has positioned correctly and reached a threshold of compression• Designed to minimize patients' perceived pain and discomfort• Intended to be available for every patient positioning• PAC’s speed profile is similar to the technologist-controlled one-Nio Color 3MP (MDNC-3421) – Barco:• High performance color IPS-TFT Color LCD• 54cm (21.3”)• 2048 x 1536 pixels (landscape)• Brightness: 900 cd/m2• Contrast ratio: 1400:1• Viewing angle: 178°• Mounted on a rotating arm for in-room access • Image PresentationeContrast allows you to choose among 6 levels to better adapt to breast morphology and radiologist display preferences:–eContrast 1 provides a “film-like” aspect withimproved visibility of the skin line– eContrast 2 to 4 provide increasing steps of imagesharpness and contrast– eContrast 5 provides a high level of sharpnessand contrast, with a very high level of tissuepenetration– eContrast 6 is adapted to very dense breast orimplants– Automatic windowing (window level and windowwidth)– Other features: zoom, roaming, inversion, flip,rotation of images, window width and level setting,annotations and measurements• In case of power failure, an Uninterruptible Power Supp ly (UPS) allows to close the examination without loss of informationConnectivity• DICOM** 3.0 platform:– Modality Worklist User– Storage Provider– Storage Commitment User– Query/Retrieve User– Basic Grayscale Print User– Verification Provider– DICOM-compliant CD, DVD-R/-RW and USB DataInterchange• Connectivity features: customizable Autopush to multiple DICOM databases, Autoprint, Autodelete based on Storage Commitment• Modality Perform Procedure Step User• Connectivity to GE Service for remote diagnostic capability • IHE Profiles: Scheduled workflow, Mammography image, Tomosynthesis profile, Portable data for imaging, Consistent time integrationQuality assurance• Complete quality control program• Automation of quality control tests: Flat Field, MTF, AOP, SNR• Test history and results can be reviewed• Data can be exported for data tracking• Automated Repeat and Reject Analysis Radiation shield• Choice between two radiation shields:– Integrated to the control console– StandaloneHigh voltage generator• Generator Integrated into the gantry for room saving • Generator type: high frequency single-phase power supply• Ripple: < 4% from peak to peak• Power: 5 kW max• Generator max rating:• 2 to 600 mAs (depending on track, filter and kV)•22 to 49 kV, in 1 kV steps depending on track • Generator protection: software monitoring tube load Standard configuration• Motorized isocentric gantry• X-ray tube with rotating Mo/Rh anode• 24 x 29 cm flat panel detector• Acquisition workstation– CD,DVD-R/-RW– 1MP or 3MP display– Control console– UPS• Pair of dual foot-pedals• Standard Face shield• 24 x 29 cm bucky with grid• 24 x 29 cm paddle• Quality control toolkit• User manual and technical documentationOptions• 1.5 and 1.8 magnification stands• Additional 24 x 29 cm paddle• 19 x 23 cm sliding paddle• 24 x 29 cm Flexible compression paddle• 19 x 23 cm Flexible & sliding compression paddle• 10x23 Sliding Implant/Small breast compression paddle • Square spot sliding compression paddle• Round spot sliding paddle• 2D Localization 19x23 Swiss Cheese sliding compression paddle• 2D Localization 19x23 sliding standard compressionpaddle•2D crosshair device• X-Ray protective shield• Bar code reader• Printers compatibility: AGFA DRYSTAR AXYS• Upgradable to Senographe Pristina 3D and/or SenoBright HD• X-ray remote control hand switch• X-ray footswitchSenographe Pristina 3DSenographe Pristina 3D is a three-dimensional imaging technology that uses a low dose short X-ray sweep around a compressed breast. The acquired projection images are processed electronically in order to reconstruct a 3D representation of the entire breast. This imaging technique is designed to separate the tissues and to reduce the overlapping of structures, which represents a limiting factor in standard 2D mammography.The 3D option is available for the Senographe Pristina platform that generates 3D and 2D images. Senographe Pristina 3D Technology• Sweep angle is 25° with 9 projections at any rotation angle between -160°/+160°• The “Step and Shoot” tube motion stops for each exposure to avoid image blur• Mo and Rh tube tracks create narrow x-ray spectra,exactly where the dose efficiency is for thin (Mo) andmedium and thick breasts (Rh)• Detector: 100 microns with no binning, high DQE in 3Dmode (IEC 62220-2-3, equivalent spectrum at 5µGy):65% (+/-2) at 0.5lp/mm and 57% (+/-2) at 2lp/mm• Automatic reconstruction of the images by using ASIR DBT iterative algorithms• The dose of a DBT (Digital Breast Tomosynthesis) view isdesigned to be equivalent to the dose of a 2D standardacquisition of the same view• Capability to reconstruct 0.5mm or 1mm distancebetween tomo-planes• 3D+2D mode allows the user to acquire in a single action a 3D sequence followed by 2D image for a given view,without releasing the compressionSenoBright HDThe SenoBright HD (Contrast Enhanced Spectral Mammography CESM) application shall enable contrast heightened breast imaging using a dual energy technique. This imaging technique can be used as an adjunct following mammography and ultrasound exams to localize a known or suspected lesion.Patient Comfort• As with previous generation GE mammography systems, patients lying in a recumbent position can be examined with SenoBright HDErgonomics designed for technologist• User can switch between standard mammography and Spectral Mammography mode during the same exam session• SenoBright HD provides a timer function to both monitor and record time after injection, which is displayed as an annotated field in the images• SenoBright HD offers Automatic Optimization of Parameters (AOP) and manual exposure modes for the dual-energy exam• S enoBright HD will automatically acquire the Spectral Mammography images for each view with a single action of the x-ray exposure control TechnologySenoBright HD chooses filtering materials depending on the operating mode and the exposure levels necessary. For the high-energy acquisition, a proprietary multi-layer filter is used to shape the resulting energies of the x-ray spectrum to those required to best highlight iodine.Energy LevelsThe energy levels may vary depending on breast thickness • 26-34 KVp for lower energy acquisition• 49 KVp for higher energy acquisition.System Power supply• Input frequency: 50Hz/60Hz• Input voltage: single-phase 200-240 V~• EATON UPS 5P650 650VASystem Weight• Gantry: 420 kg• Control Station without monitors: 160 kg Environmental conditions• Temperature range: 15° to 30°C• Humidity range: 10% to 80%• Atmospheric pressure range: 70 kPa to 106kPa(0 to 3000m altitude)Screening ProtocolFor reference, in the US a DBT screening examination may consist of one of the following combinations (CC: craniocaudal, MLO: mediolateral oblique):- a 2D CC view and a 3D DBT MLO view, or- a 3D DBT image set consisting of CC and MLO views, and a 2D synthesized image set consisting of CC and MLO V-Preview images.V-Preview is the 2D synthesized image generated by GE SenoIris mammography software from GE DBT images.Note: Breast cancer screening may be regulated by country specific rules. Please refer to competent Healthcare Authorities for guidanceWireless Footswitch OptionThe wireless footswitch is available on the Senographe Pristina platform. The footswitch includes pedals to activate lift up, lift down, compression and decompression functionalities. The communication range between the footswitch and the receiver shall be located within 1.5m radius from the gantry.Mobile OptionA Mobile Mounting Device is available for Senographe Pristina 2D and 3D to allow its installation and transportation in a mobile unitWorkflow OptionsThe Senographe Pristina is compatible with iCAD Second Look (2D CAD), iCAD Tomo Detection 1.0 (3D CAD) and iCAD ProFound AI for Tomo (3D CAD)Senographe PristinaNOTE:- Weights and dimensions may vary slightly depending on equipment configuration.Senographe Pristina, PAC, Wireless footswitch, Mobiles and iCAD are not available in all countries. Please refer to your GE Healthcare sales representative.1885m775368Maximum HeightGantry BasePlateM ax imM ax im uData subject to change.Marketing Communications GE Medical SystemsSociété en Commandite Simple au capital de 85.418.040 Euros 283, rue de la Minière, 78530 Buc France RCS Versailles B 315 013 359A General Electric company, doing business as GE HealthcareUK: 0800 0329201Spain: 0900 993620 Germany************France: 0800 908719Austria: 0800 291888 SwitzerlandItaly: 0800 786947 German: 0800 837279French: 0800 837279GE, the GE Monogram, and imagination at work are trademarks of the General Electric Company*Trademark of General Electric Company** DICOM is a trademark of National Electrical Manufacturers Association.All other trademarks, service marks, company names and product names are the property of their respective owners© 2016-2019 Copyright GE Healthcare。
介绍pubsubPro
– bind(eventtype, handler, [containAsyncOp]);
• __MODULE_EVENT_LIST__ • _bindXxxx inner methods dynamically generated based on __MODULE_EVENT_LIST__
pubsubPro.js
– Deferred：an unfinished task; – Promise: an undecided value;
Promise/Deferred
• Spec clauses
– Has a function as a value for the property ‘then’, which must be return a promise object. – Promise has 3 state(unfulfilled, fulfilled, failed) – Promise only contain the decided handler(done, fail, progress, etc.) rather than method that can change its status.
介绍pubsubpro千金女贼剧情介绍何以笙箫默剧情介绍武媚娘传奇剧情介绍长大剧情介绍千金女贼分集剧情介绍活色生香剧情介绍自动挡车档位介绍好大一个家剧情介绍别叫我兄弟剧情介绍
pubsubPro.js
An enhanced pub/sub event interface
Outline
• Async programming
• Using Promise/Deferred
– The informing and value passing mechanism are what we need in this case.
一次排查@CacheEvict注解失效的经历及解决
⼀次排查@CacheEvict注解失效的经历及解决⽬录排查@CacheEvict注解失效下⾯是我通过源码跟踪排查问题的过程⼩结⼀下说说spring全家桶中@CacheEvict⽆效情况举个例⼦排查@CacheEvict注解失效我简单看了⼀下《Spring实战》中的demo，然后就应⽤到业务代码中了，本以为如此简单的事情，竟然在代码提交后的1个周，被同事发现。
selectByTaskId()⽅法查出来的数据总是过时的。
代码如下：@Cacheable("taskParamsCache")List<TaskParams> selectByTaskId(Long taskId);// ...// ...@CacheEvict("taskParamsCache")int deleteByTaskId(Long taskId);想要的效果是当程序调⽤selectByTaskId()⽅法时，把结果缓存下来，然后在调⽤deleteByTaskId()⽅法时，将缓存清空。
经过数据库数据对⽐之后，把问题排查的⽅向定位在@CacheEvict注解失效了。
下⾯是我通过源码跟踪排查问题的过程在deleteByTaskId()⽅法的调⽤出打断点，跟进代码到spring⽣成的代理层。
@Override@Nullablepublic Object intercept(Object proxy, Method method, Object[] args, MethodProxy methodProxy) throws Throwable {Object oldProxy = null;boolean setProxyContext = false;Object target = null;TargetSource targetSource = this.advised.getTargetSource();try {if (this.advised.exposeProxy) {// Make invocation available if necessary.oldProxy = AopContext.setCurrentProxy(proxy);setProxyContext = true;}// Get as late as possible to minimize the time we "own" the target, in case it comes from a pool...target = targetSource.getTarget();Class<?> targetClass = (target != null ? target.getClass() : null);List<Object> chain = this.advised.getInterceptorsAndDynamicInterceptionAdvice(method, targetClass);Object retVal;// Check whether we only have one InvokerInterceptor: that is,// no real advice, but just reflective invocation of the target.if (chain.isEmpty() && Modifier.isPublic(method.getModifiers())) {// We can skip creating a MethodInvocation: just invoke the target directly.// Note that the final invoker must be an InvokerInterceptor, so we know// it does nothing but a reflective operation on the target, and no hot// swapping or fancy proxying.Object[] argsToUse = AopProxyUtils.adaptArgumentsIfNecessary(method, args);retVal = methodProxy.invoke(target, argsToUse);}else {// We need to create a method invocation...retVal = new CglibMethodInvocation(proxy, target, method, args, targetClass, chain, methodProxy).proceed();}retVal = processReturnType(proxy, target, method, retVal);return retVal;}finally {if (target != null && !targetSource.isStatic()) {targetSource.releaseTarget(target);}if (setProxyContext) {// Restore old proxy.AopContext.setCurrentProxy(oldProxy);}}}通过getInterceptorsAndDynamicInterceptionAdvice获取到当前⽅法的拦截器，⾥⾯包含了CacheIneterceptor，说明注解被spring检测到了。
泛型类型（generictypes）
泛型类型（generic types）Concepts: classes, structures, interfaces can be generic, generic types have type parameters, and they are placeholders to be completed later.(for example, a generic class is still a class, just a type parameter.)Generic types, also known as construction types, have open construction types and closed construction typesThe build type of the opening method has at least one type, the parameter is a placeholder, and no specific type of constraint is used(such as public, class, teacher<T>{})If the combination of a generic method and a non generic method is ambiguous, a non generic method is called.Encapsulates a method that has a parameter and returns the specified type of the TResult parameterPublic delegate TResult Func<in T, out TResult>T ARG)Func<T, TResult> generic delegateEncapsulates a method that has a parameter and returns the type value specified by the TResult parameter.Namespace: SystemAssembly: System.Core (in System.Core.dll)grammarPublic, delegate, TResult, Func<T, TResult>T ARG)Type parameterTThe parameter type of the method that this delegate encapsulates.TResultThe return value type of the method encapsulated by this delegate.parameterARGType: TThe parameters of the method encapsulated by this delegate.Return valueType: TResultThe return value of the method encapsulated by this delegate.RemarksYou can use this delegate to construct a method that can be passed in a parameter, without explicitly declaring a custom delegate. This method must correspond to the method signature defined by this delegate. That is, the encapsulation method must have a parameter passed to it by value, and must return the value.Be careful：To refer to a method that has a parameter and returns void (or to refer to a method declared in Visual Basic instead of being declared as Function), use the generic Action<T> Sub delegate.When using Func<T, TResult> delegate, there is no need to explicitly define a delegate with a method that encapsulates only one parameter. For example, the following code explicitly declares a delegate called ConvertMethod and assigns a reference to the UppercaseString method to its delegate instance.Using System;Delegate string ConvertMethod (string inString);Public class DelegateExample{Public, static, void, Main (){Delegate to reference UppercaseString method / / InstantiateConvertMethod convertMeth = UppercaseString;String name = "Dakota"";Use delegate instance to call UppercaseString / / methodConsole.WriteLine (convertMeth (name));}Private, static, string, UppercaseString (string, inputString){Return, inputString.ToUpper ();}}The following example simplifies this code by using the Func<T TResult> delegate instead of explicitly defining a new delegate and assigning the naming method to the delegate.Using System;Public class GenericFunc{Public, static, void, Main (){Delegate to reference UppercaseString method / / InstantiateFunc<string, string>, convertMethod = UppercaseString;String name = "Dakota"";Use delegate instance to call UppercaseString / / methodConsole.WriteLine (convertMethod (name));}Private, static, string, UppercaseString (string, inputString){Return, inputString.ToUpper ();}}You can also use Func<T and TResult> delegates in C# with anonymous methods as shown in the following example. For an overview of anonymous methods, see the anonymous methods (C# Programming Guide)Using System;Public class Anonymous{Public static void Main (){Func<string, string> convert = delegate (string s){return, s.ToUpper ();};String name = "Dakota"";Console.WriteLine (convert (name));}}You can also assign lambda expressions to Func<T, TResult> delegate, as shown in the following example. For a brief introduction to lambda expressions, see Lambda expressions and Lambda expressions (C# programming guidelines)Using System;Public class Lambdaexpression_r_r_r{Public, static, void, Main (){Func<string, string> = s = > s.ToUpper (convert);String name = "Dakota"";Console.WriteLine (convert (name));}}The base type of the Lambda expression is one of the generic Func delegate. This allows you to pass the lambda expression in parameter form without assigning it to the delegate explicitly. Especially, because many types of methods in the System.Linq namespace Func<T, TResult> parameters, so it can pass a lambda expression to these methods, without explicitly instantiate Func<T, commissioned by TResult>.SampleThe following example demonstrates how to declare and use Func<T, TResult> delegate. This example declares a Func<T, TResult> variable and assigns it a lambda expression that converts characters from strings to uppercase. Subsequently, the delegate that encapsulates this method is passed to the Select method to change the string in the string array to uppercase.Using System;Using System.Collections;Using System.Collections.Generic;Using System.Linq;Static class Func{Static void Main (string[] args){Declare a Func variable and assign / a lambda expression_r_r_r to theVariable. The method takes a string / and converts it to uppercase.Func<string, string> = STR = > str.ToUpper (selector);An array of strings. / / CreateString[], words = {, orange, apple, Article, elephant};Query the array and select Strings / according to the selector method.IEnumerable<String> aWords = words.Select (selector);The results to the console. / / OutputForeach (String, word, in, aWords)Console.WriteLine (word);}}Zhongxie and the definition of a generic variable inverter:Animal animal = new (Dog); / / implicit type conversionDog dog = animal (Dog); / / type coercionIMyInterface<Animal> iAnimal = null;IMyInterface<Dog> iDog = null;IAnimal = iDog; / / "sub class" to "superclass" conversion, namely generic interface covariantIDog = iAnimal; / / "superclass" to "sub class" conversion, namely generic interface inverterGeneric type constraints have:Derived constraints: the derived constraints require that the type is actually associated with the specified typeExamples: ZClass<T> where T:YClass<XClass> or XClass<T1 T2>, where T1:T2Interface constraints: type constraints can also require type arguments to implement an interface.Value type constraint: restrict a type parameter to a value type,The value type constraint uses the struct keyword.Reference type constraint: defines a type parameter as a reference type. (class, interface, delegate, string, array) are referred to as reference types, and the reference type is bound by using class.Constructor constraint: the constructor uses the keyword NEW. (new keyword has three uses, no operator modifier definition constraint)In addition to value types, the following types cannot be used as constraintsSeale sealed class, open constructor primitive type, system.ArraySystem.DelegateSystem.EnumSystem.valueType。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
4.0 SummaryIn this position paper we have proposed an aspect language that supports the expression of communication preferences even if they have a dynamic nature. Sometimes it is better that aspects remain run-time entities, i.e. dynamic aspects. We have described some examples that can benefit from dynamic aspects, based on the SMove case study. The SMove case clearly shows the practical need for such dynamic aspects.We argue that a survival of aspects at run-time is in many cases a necessary precondition to ensure maximal flexibility and to allow an aspect to adapt itself based on execution-time information. A feasible approach to handle such dynamic aspects is to implement them using meta-objects.5.0 ReferencesAOP97 F. Matthijs, W. Joosen, B. Vanhaute, B. Robben, P. Verbaeten. “Aspects should not die.” In European Conference on Object-Oriented Programming, Work-shop on Aspect-Oriented Programming. 1997.Kiczales G. Kiczales. “Towards a New Model of Abstraction in Software Engineering.”In Proceedings of the International Workshop on New Models in SoftwareArchitecture ‘92; Reflection and Meta-Level Architecture. 1992.SMdesign P. Kenens, S. Michiels, E. Truyen, S. V an Baelen, W. Joosen, F. Matthijs, P.Verbaeten. “Communication System: System Design Document.”ConfidentialInformation.1998.SMapi S. Van Baelen, E. Truyen, P. Kenens, S. Michiels, W. Joosen, F. Matthijs, E.Steegmans, P. Verbaeten. “The Development of an Application ProgrammingInterface for the SMove Project”.Confidential Information. 1998.To allow this, we need a more powerful construct than the when-clause in Figure4. By using the dynamic keyword followed by a class name, it becomes possible to encap-sulate in this class, an entire preference selection algorithm instead of a simple condition. It can be used for instance to couple communication preferences with individual objects, instead of with classes only.FIGURE 5. A dynamic preferenceAn example of this construct is shown in Figure5. For every invocation to a vehicle, the preference chooser will be asked to return the appropriate preference for that invocation, depending on the current circumstances. The returned preference depends on the invoked vehicle.Figure7 shows the abstract syntax of the dynamic preference aspect language that we used in the examples described above. This language extends the language we have pro-posed in section 3.2. It enables to differentiate between different run-time situations.3.4 Aspect weavingThe first aspect program shown in Figure2 illustrates a static communication preference aspect. The specified preferences are static for all vehicles (all vehicles are treated the same), at all times (preferences will not change at run-time). A specialized aspect weaver can weave the aspect in the application code at compile-time.The dynamic communication aspect in section 3.3 can not always be woven at compile-time. When the choice of preference depends on information that is only available at run-time, this preference cannot be known at compile-time. An approach to handle such dynamic aspects is to weave them at run-time. This can be accomplished a.o. by a meta-object protocol [Kiczales]. In this case, remote invocations are reflected to a metalevel where communication preferences can be added based on compile-time, as well as run-time information.FIGURE 3. Abstract syntax of static preference aspect languageShortcomings of this static approach. Communication preferences can not always be statically defined. They can depend on external circumstances, like e.g. the time of the day or the current position of the vehicle. When communication at peak hour is more expen-sive than communication at off-hour, cheap communication at peak hour and fast commu-nication at off-hour may be preferred. It is also possible that a user wants to change the communication preferences when the vehicle crosses a border.3.3 Dynamic preferencesTo express more sophisticated preferences which capture the problems described above we introduce dynamic preferences.An example of an application with dynamic communication preferences is a vehicle con-trol application that allows a transport company to monitor the current location of its vehi-cles. The aspect program in Figure4 accomplishes the communication preferences for this application. Communication to vehicles for instance is handled by a PeakHourPref-erence: a CostPreference is preferred during peak hours, while communication will be based on a FastDeliveryPreference during off-hours.Now suppose vehicles have different kinds of loads. Preferences could be based on the load a vehicle is carrying, e.g. a dangerous or an unimportant load. It is crucial that a truck with a dangerous load can be reached quickly under all circumstances, while this is less important in case of a regular truck. Communication to vehicles that carry a dangerous load should be handled by a FastDeliveryPreference.our specific language to support complex dynamic preferences, we rely on an existing lan-guage for such preferences.3.1 AttributesThe SMove architecture enables applications to suggest communication preferences (like speed and cost of communication) that influence the selection of a communication device. We introduce some attributes, which will be used in the aspect language, that enable us to express the communication aspect in a declarative manner. Some examples of attributes are:•COST: communication with low cost is preferred•SPEED: high performance communication is preferred•FAST_DELIVERY: low communication delay is preferred•PROVIDER: a specific communication provider is preferred3.2 Static preferencesSome applications have communication preferences that are statically defined (this means known at compile-time, and the same for all vehicles). An example is an application for remote control and immobilization of vehicles. Such an application can for instance be used by the police. A reasonable communication preference could be to communicate as cheaply as possible, but for immobilization of a vehicle (e.g. when it is reported as stolen), low latency communication1 is preferred.The aspect program in Figure2 is an implementation of the static communication prefer-ence explained above. By mentioning the COST attribute as default, we state that a low cost communication device is preferred for all remote invocations, except for those methods that are explicitly specified in the aspect program. In this example, this is done by attaching the FAST_DELIVERY attribute to the immobilize method. This means that immobilization messages are always sent by a low latency communication channel.The abstract syntax in Figure3 makes it possible to implement such a static communica-tion strategy.1.Certain cheap communication types can have delays of several hours for long distance communication.API (Application Programming Interface) that hides the specific underlying communica-tion devices. They can only indicate high level communication preferences, like commu-nication cost, communication speed, etc... This way, applications do not have to be rewritten whenever an underlying communication device changes or when a new one becomes available.2.2 Flexible communicationCommunication with a vehicle happens by means of so called features. A feature is an object that encapsulates a service provided by a vehicle (e.g. a positionfeature that sup-ports requests for, and control of position coordinates, a speedfeature for requesting and controlling the speed of a vehicle, etc.). Each vehicle can have a different set of supported features. These features can be added/removed per vehicle, at run-time. Applications can interact with vehicles by invoking operations on the feature-objects that are available. Invocations on features are physically routed over one of many possible wireless commu-nication channels. Each of these communication channels has its own specific characteris-tics. An important characteristic of the SMove platform is that the selection of a specific communication device can be influenced by application-specific preferences. Such prefer-ences can even differ for each invocation of a vehicle.Communication preferences are scattered over different levels of the system, what leads to a problem of encapsulation. At the application level, preferences are bounded to invoca-tions and in the protocol stack the actual device selection takes place. This means that communication preferences cross-cut the system component boundaries. They are related to the essential semantics of the SMove platform and can not be clearly encapsulated in some kind of component. The aspect paradigm helps to separate communication prefer-ences from the functional code!3.0 An aspect language for communication preferencesThe SMove platform can be viewed from many perspectives, showing us different kinds of aspects related to communication, distribution, performance, synchronization, logging, accounting, etc. We describe a way to handle communication preferences using the aop approach. We propose a specific aspect language that enables programmers to add static as well as dynamic communication preferences to remote invocations. Instead of extendingAn AOP Case with Static and DynamicAspectsPeter Kenens, Sam Michiels, Frank Matthijs, Bert Robben, Eddy Truyen, BartVanhaute, Wouter Joosen, Pierre Verbaeten{Peter.Kenens, Sam.Michiels}@cs.kuleuven.ac.beDept. of Computer Science - K.U.LeuvenCelestijnenlaan 200A B-3001 LEUVEN BELGIUM1.0 IntroductionAspect-oriented-programming (aop) is a promising new approach where the description of a complex system/application is enchanced with various aspects, related to communica-tion properties, distribution, synchronization, etc. All aspects can be described separately and are brought together by using a so-called weaver. Mostly, this is performed at com-pile-time, what makes that aspects disappear in the final software version. We argue that in some cases aspects should remain run-time entities in order to capture the dynamic prop-erties of an application [AOP 97]. We believe there is a need for dynamic aspects, e.g. strongly related to objects, which are clearly run-time entities.Our experiences in a project called SMove clearly show the practical need for such dynamic aspects. In this position paper we propose an aspect language that supports a communication aspect with a dynamic nature. We describe some examples that can benefit from dynamic aspects, based on the SMove case study ([SMdesign] [SMapi]). We hope that feedback on our approach of dynamic aspects can inspire the ongoing implementa-tion.This position paper is structured as follows: in section 2 we shortly introduce the SMove platform. Section 3 describes the proposed aspect language. We summarize in section 4.2.0 The SMove platform2.1 ArchitectureThe SMove architecture consists of Application Centers and vehicles (see Figure1). The goal of the platform is to support the development of applications that can communicate with vehicles through a number of wireless communication channels, a.o. ERMES and GSM. It enables the use of a wide variety of applications, such as remote vehicle immobi-lization, traffic monitoring, localization, border control, toll collection, etc. that can oper-ate under a wide range of conditions (e.g. in a parking garage,...) and with different costs. To develop these applications in a cost effective way, programmers can use the SMove。