| M. Sander, H. Schmidt, W. Schroder-Preikschat, "Naming in the Peace Distributed Operating System", International Workshop on "Communication Networks and Distributed Operating Systems within the Space Environment", pp. 293302, ESTEC, Noordwijk, The Netherlands, October 24-26, 1989 |
....as argument of a clerk s constructor (Fig. 14) This class Mailbox: public reference, public: Mailbox(place = place( mailbox 88 7.8. 92 ) Figure 13: Signature of a Likeness Constructor initialization performs automatic binding to a suitable clerk by means of the Peace name service [14]. The supplied place argument of the likeness constructor (Fig. 13) is derived from an unique class describing unique identifiers. The construction of a place object with a string as constructor argument automatically performs symbolic binding by means of the supplied string. Generated default ....
M. Sander, H. Schmidt, and W. SchroderPreikschat, "Naming in the PEACE Distributed Operating System," in International Workshop on Communication Networks and Distributed Operating Systems within the Space Environment, (Nordwijk, The Netherlands) , Oct. 1989.
....be found as argument of a clerk s class Neuron: public reference, public: Neuron (place = place( #)neuron 88 68787898 ) Figure 16: Signature of a Likeness Constructor constructor (Fig. 17) This initialization will perform automatic binding by means of the Peace name service [8]. The supplied place argument of the likeness constructor (Fig. 16) is derived from a unique class describing unique identifiers. The construction of a place object with a string as constructor argument will perform symbolic binding by means of the supplied string. Since default arguments of a ....
....a clerk resides inside the same address space (Fig. 20) as the requested likeness. neuronclerk server; a neuron clerk . Neuron a (1.3, server) place a on server Figure 20: Direct Placement 5. 4 Scoped Placement In Peace each active object (process) is implicitly tied to a name space [8]. The default binding scheme automatically refers to the default name space. The default binding scope may now be explicitly overridden. Scoped binding (Fig. 21) is similar to default binding, but, additionally, gives a hint, which name space should be used for binding. Therefore scoped placement ....
M. Sander, H. Schmidt, and W. Schroder-Preikschat, "Naming in the peace distributed operating system," in International Workshop on Communication Networks and Distributed Operating Systems within the Space Environment, (Nordwijk, The Netherlands), oct 1989.
....makes no sense to work with fixed addresses, because their values are location dependent and therefore not predictable. Instead, the clerk s address is determined dynamically. For this binding mechanism a decentralized naming service is used. Naming in Peace is realized by one or more name servers [10]. Each service providing thread registers a well defined symbolic identifier in the name space and associates it with its own address (name export) The client queries the name space during object construction for that name (name import) and learns the address this way. The names administered by ....
M. Sander, H. Schmidt, W. Schroder-Preikschat, "Naming in the Peace Distributed Operating System", International Workshop on "Communication Networks and Distributed Operating Systems within the Space Environment", pp. 293302, ESTEC, Noordwijk, The Netherlands, October 24-26, 1989
....makes no sense to work with fixed addresses, because their values are location dependent and therefore not predictable. Instead, the clerk s address is determined dynamically. For this binding mechanism a decentralized naming service is used. Naming in Peace is realized by one or more name servers [12]. Each service providing thread registers a well defined symbolic identifier in the name space and associates it with its own address (name export) The client queries the name space during object construction for that name (name import) and learns the address this way. The names administered by ....
M. Sander, H. Schmidt, W. Schroder-Preikschat, "Naming in the Peace Distributed Operating System", International Workshop on "Communication Networks and Distributed Operating Systems within the Space Environment", pp. 293302, ESTEC, Noordwijk, The Netherlands, October 24-26, 1989
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC