Using BINS for inter-process communication

ABSTRACT

A bin is essentially a message drop, used to implement inter-process communications in the FRANK programming language. The use of bins provides three distinct advantages over traditional message passing systems.1) relative anonymity,2) multiple servers,3) enhanced compile time checking. (relative to systems like Thoth[3]).This paper discusses the rationale behind bins and the possible implementation strategies under examination. Finally, it gives two examples using bins which will illustrate the concept.

REFERENCES

• 1: Brinch Hansen, Per.. <u>The Programming Language Concurrent Pascal</u> "IEEE Transactions on Software Engineering", June 1975, pp. 199--207.
• 2: Cashin, Peter M.. <u>Inter Process Communication</u> Internal B.N.R. document, Reference: 8005014, June 1980.
• 3: David R. Cheriton, The Thoth System, Elsevier Science Inc., New York, NY, 1982
• 4: Ditchfield, Glen, etal. <u>Preliminary FRANK Reference Manual</u>. (to be published as a University of Manitoba Scientific Report)
• 5: C. A. R. Hoare, Communicating sequential processes, Communications of the ACM, v.21 n.8, p.666-677, Aug. 1978 [doi>10.1145/359576.359585]
• 6: C. A. R. Hoare, Monitors: an operating system structuring concept, Communications of the ACM, v.17 n.10, p.549-557, Oct. 1974 [doi>10.1145/355620.361161]
• 7: Mitchell, James G., etal. <u>Mesa Language Manual Version 5.0</u> XEROX Palo Alto Research Center report #CSL-79-3.
• 8: Nelson, Bruce J., <u>Remote Procedure Call</u> XEROX Palo Alto Research Center report #CSL-81-9.