Local Class Name Space Facility for Worldwide Object-Oriented Distributed Systems Environment

  • Toshihiro Nishioka
  • Yoichi Hamazaki
  • Michiharu Tsukamoto
Session A-2: Distributed Objects Environments
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1274)


When writing a program to be executed in the worldwide object-oriented distributed systems environment, the source code may include class names developed at other sites. In this case, using the class name as a runtime class identifier, which should be globally unique, may cause problems such as: 1) The same class name representing a different class is found in another site. 2) Classes using different versions of a class cannot work together. To tackle these problems, the authors proposed and implemented a local class name facility called ‘chool. The school facility separates the compile time class name and the runtime class identity. This paper describes our design and implementation of the school and the runtime class identity in the OZ++ system: a worldwide object-oriented distributed systems environment developed by the authors.


Local Class Runtime System Source File Object Code Server Object 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Campione, M. and Walrath, K.: “The Java Tutorial — Object-Oriented Programming for the Internet,” The Java Series, Addison and Wesley, ISBN 0-201-63454-6, 1996.Google Scholar
  2. 2.
    The Object Management Group: “The Common Object Request Broker: Architecture and Specification,” OMG Document, 1991.Google Scholar
  3. 3.
    Hirano S. and Tsukamoto M.: “Building a Portable ORB for Java,” IPSJ technical note, OS 73–10, 1996 (in Japanese).Google Scholar
  4. 4.
    Hamazaki Y., Tsukamoto M., Onishi M. and gNiibe Y.: “The Object Communi cation Mechanisms of OZ++: An Object-Oriented Distributed Systems Environ ment,” Proc. of 9th ICOIN, pp 425–430, 1994.Google Scholar
  5. 5.
    Gosling, J. and McGilton, H.: “The Java Language Environment — A White Paper,” 1996.Google Scholar
  6. 6.
    Gosling, J., Joy, B. and Steele, G.: “The Java Language Specification,” The Java Series, Addison and Wesley, ISBN 0-201-63451-1, 1996.Google Scholar
  7. 7.
    Tsukamoto M., Hamazaki Y., Nishioka T. and Otokawa H.: “The Version Man agement Architecture of an Object-Oriented Distributed Systems Environment: OZ++,” in Briot, J.-P., Geib, J.-M. and Yonezawa A. (Eds.): “Object-Based Paral lel and Distributed Computation,” LNCS 1107, Springer-Verlag, pp 310–328, 1996.Google Scholar
  8. 8.
    Tsukamoto M., Hamazaki Y., Otokawa H. and Nishioka T.: “The Design and Imple mentation of an Object-oriented Distributed System Based on Sharing and Trans ferring of Classes,” Trans. of Information Processing Society of Japan, vol. 37, no. 5, pp 853–864, 1996 (in Japanese).Google Scholar
  9. 9.
    Waldo, J., Wyant, G., Wollrath, A. and Kendall, S.: “A Note on Distributed Com puting,” Sun Microsystems Laboratories Technical Report, TR-94–29, 1994.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1997

Authors and Affiliations

  • Toshihiro Nishioka
    • 1
  • Yoichi Hamazaki
    • 2
  • Michiharu Tsukamoto
    • 2
  1. 1.Mitsubishi Research Institute, Inc.TokyoJapan
  2. 2.Electrotechnical LaboratoryTsukuba, IbarakiJapan

Personalised recommendations