{"title":"消息交换系统中的保护和同步","authors":"Jon Livesey, Eric Manning","doi":"10.1016/0376-5075(83)90017-X","DOIUrl":null,"url":null,"abstract":"<div><p>In any computer system it is valuable to have methods for enforcing expected behaviour at runtime. (Capabilities and object-oriented architectures are mechanisms commonly used to address the problem.) In a message-switched system, all inter-process communication is done by the transmission of messages, and the problem of enforcing expected behaviour can be reduced to the problem of enforcing expected patterns of message transmission.</p><p>In this paper we give a method, called the <em>Task Graph Language</em>, for expressing expected patterns (policy) of message transmission. Such an expression is quite independent of the actual programs which pass messages, and can be used at runtime to check the validity of observed behaviour. The <em>mechanism</em> we provide to perform the runtime checking of observed <em>vs.</em> expected behaviour is called <em>Token Lists</em>.</p><p>This mechanism requires no esoteric hardware support and it can be used in both distributed and centralized systems. From another perspective, the user is provided with two independent, hence mutually redundant, ways to express his intent (the programs which pass messages and the Task Graph Language description), and the two expressions of intent are compared or matched at runtime as a checking mechanism. From still another perspective, the Task Graph Language and Token Lists permit a centralized representation of distributed control.</p></div>","PeriodicalId":100316,"journal":{"name":"Computer Networks (1976)","volume":"7 4","pages":"Pages 253-268"},"PeriodicalIF":0.0000,"publicationDate":"1983-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1016/0376-5075(83)90017-X","citationCount":"1","resultStr":"{\"title\":\"Protection and synchronisation in a message-switched system\",\"authors\":\"Jon Livesey, Eric Manning\",\"doi\":\"10.1016/0376-5075(83)90017-X\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"<div><p>In any computer system it is valuable to have methods for enforcing expected behaviour at runtime. (Capabilities and object-oriented architectures are mechanisms commonly used to address the problem.) In a message-switched system, all inter-process communication is done by the transmission of messages, and the problem of enforcing expected behaviour can be reduced to the problem of enforcing expected patterns of message transmission.</p><p>In this paper we give a method, called the <em>Task Graph Language</em>, for expressing expected patterns (policy) of message transmission. Such an expression is quite independent of the actual programs which pass messages, and can be used at runtime to check the validity of observed behaviour. The <em>mechanism</em> we provide to perform the runtime checking of observed <em>vs.</em> expected behaviour is called <em>Token Lists</em>.</p><p>This mechanism requires no esoteric hardware support and it can be used in both distributed and centralized systems. From another perspective, the user is provided with two independent, hence mutually redundant, ways to express his intent (the programs which pass messages and the Task Graph Language description), and the two expressions of intent are compared or matched at runtime as a checking mechanism. From still another perspective, the Task Graph Language and Token Lists permit a centralized representation of distributed control.</p></div>\",\"PeriodicalId\":100316,\"journal\":{\"name\":\"Computer Networks (1976)\",\"volume\":\"7 4\",\"pages\":\"Pages 253-268\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1983-08-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"https://sci-hub-pdf.com/10.1016/0376-5075(83)90017-X\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Computer Networks (1976)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://www.sciencedirect.com/science/article/pii/037650758390017X\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Computer Networks (1976)","FirstCategoryId":"1085","ListUrlMain":"https://www.sciencedirect.com/science/article/pii/037650758390017X","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Protection and synchronisation in a message-switched system
In any computer system it is valuable to have methods for enforcing expected behaviour at runtime. (Capabilities and object-oriented architectures are mechanisms commonly used to address the problem.) In a message-switched system, all inter-process communication is done by the transmission of messages, and the problem of enforcing expected behaviour can be reduced to the problem of enforcing expected patterns of message transmission.
In this paper we give a method, called the Task Graph Language, for expressing expected patterns (policy) of message transmission. Such an expression is quite independent of the actual programs which pass messages, and can be used at runtime to check the validity of observed behaviour. The mechanism we provide to perform the runtime checking of observed vs. expected behaviour is called Token Lists.
This mechanism requires no esoteric hardware support and it can be used in both distributed and centralized systems. From another perspective, the user is provided with two independent, hence mutually redundant, ways to express his intent (the programs which pass messages and the Task Graph Language description), and the two expressions of intent are compared or matched at runtime as a checking mechanism. From still another perspective, the Task Graph Language and Token Lists permit a centralized representation of distributed control.