G. Ballintijn, M. van Steen, and A. S. Tanenbaum. Scalable naming in global middleware. In 13th Int'l Conf. on Parallel and Distributed Computing Systems (PDCS-2000), 2002.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....preference: traders explore the network on demand, while serving a request, and off demand, whenever necessary. Changes of trader s state (e.g. services provided or collaboration policies) are propagated through flooding throughout the network. The Globe project [41] proposes a naming service [5] that transforms an URL into a location independent unique identifier. This way, the location service deals well with object migration. Among the distributed resource sharing systems that do not use global names for resource discovery is Condor s Matchmaker [32] resource descriptions and ....

BALLINTIJN, G., VAN STEEN, M. V., AND TANENBAUM, A. Scalable naming in global middleware. In 13th Int'l Conf. on Parallel and Distributed Computing Systems (PDCS-2000.

....on resource discovery: a naming service, that given an URL, returns a location independent unique identifier, and a location service, that given an object identifier, returns the object location. Names are therefore location independent to support object (service) migration. The naming service [5] is based on the Unix directory structure: each directory can resolves the names of the objects it stores. Hence, a lookup for the file a b c involves repeatedly name and location lookups for each of the objects a, b, and c. The location service [52] in Globe is based on a hierarchy, where each ....

BALLINTIJN, G., VAN STEEN, M. v., AND TANENBAUM, A. Scalable naming in global middleware. In 13th Int'l Conf. on Parallel and Distributed Computing Systems (PDCS-2000.

....step, the symbolic name of the software package object is resolved to a binary object handle. The object handle of a software package object is its permanent identifier that does not change during the lifetime of the object. This resolution step is carried out by the Globe Naming Service (GNS) [2]. In the second step, the object handle of the package object is mapped to the contact address of its nearest replica. This contact address contains, among other items, the IP address of the object server running the replica. We have developed a special service for mapping the ....

....on authenticity of the distributed software. Therefore, downloading users must retrieve the objectname to package binding from a trusted source, for example, the package s well known Web site. We intend to replace the DNS based prototype with an implementation based on distributed shared objects [2] in the future. The basic functionality of the Globe Location Service, that is, mapping location independent object handles to contact addresses in a scalable way has been completely implemented. This implementation is described in full detail in [16] The Globe Infrastructure Directory Service ....

Ballintijn G, van Steen M, Tanenbaum AS. Scalable naming in global middleware. In Proceedings of the 13th Int'l Conf. on Parallel and Distributed Computing Systems (PDCS-2000), Chaudhry G, Sha E (eds.). ISCA: Cary, NC; 624--631.

....name of the software package object is resolved to a locationindependent object handle. The object handle of a softwarepackage object is its permanent identifier that does not change during the lifetime of the object [10] This resolution step is carried out by the Globe Naming Service (GNS) [1]. In the second step, the object handle of the package object is mapped to the contact address of its nearest replica. This contact address contains, among other items, the IP address of the object server running the replica. We have developed a special service for mapping the locationindependent ....

G. Ballintijn and M. van Steen. "Scalable Naming in Global Middleware." In Proc. 13th Int'l Conf. on Parallel and Distributed Computing Systems, pp. 624--631, Las Vegas, Aug. 2000. ISCA.

....problems arise in DNS that prevent our HFN resolution mechanism from scaling further. If we want to support more than 10 7 resources, or resources that are impopular or mobile, we need to replace DNS with a more scalable name service. We describe the design of such a naming service in [2]. A different problem with using DNS as the name service in our scheme, is that it places restrictions on the syntax of the HFN name space. Since we need to translate our HFN names to DNS names, we can support only the small subset of the ASCII character set that is allowed by DNS. Given the ....

....number of specific kind of resource. Future work will consist of using our naming scheme in larger experimental setups to gain more experience. Security is currently designed, by still needs to be implemented. A larger project will be the implementation of our own name service, as described in [2], to replace DNS. ....

G. Ballintijn and M. van Steen. Scalable Naming in Global Middleware. Technical Report IR-464, Vrije Universiteit, Amsterdam, The Netherlands, Oct. 1999.

....DNS might become overloaded. If we want to support mobile resources, the caching mechanism might cache mappings in the wrong place. If we want to support a more general resource model, we need to replace DNS with a more scalable name service. We describe the design of such a naming service in [1]. A different problem with using DNS as the name service in our scheme, is that it places restrictions on the syntax of the HFN name space. Since we need to translate our HFN names to DNS names, we can support only the small subset of the ASCII character set that is allowed by DNS. Given the ....

G. Ballintijn and M. van Steen. Scalable Naming in Global Middleware. In Proc. Sixth Int'l Conf. on Parallel and Distributed Computing Systems, Las Vegas, Aug. 2000.

....passed to a DNS resolver as though it were a regular host name. The resolution eventually always reaches a Globe name server (e.g. the server for globe.cs.vu.nl) which resolves the remainder of the name to the appropriate object handle. Details on the name service implementation can be found in [5]. globe.cs.vu.nl foo object1 kermit bar baz Globe Domain DNS Domains Name Domain System globe.twi.tudelft.nl globe.org Figure 5: DNS based Globe name space 3.2 Location service An object handle is resolved to one or more contact addresses by the location service. As mentioned, an ....

G. Ballintijn and M. van Steen. "Scalable naming in global middleware." Technical Report IR-464, Vrije Universiteit Amsterdam, the Netherlands, Oct. 1999. http://www.cs.vu.nl/pub/papers/globe/IR-464.99.ps.

No context found.

G. Ballintijn, M. van Steen, and A. S. Tanenbaum. Scalable naming in global middleware. In 13th Int'l Conf. on Parallel and Distributed Computing Systems (PDCS-2000), 2002.

No context found.

Ballintijn, G., Steen, M. v., and Tanenbaum, A. Scalable naming in global middleware. In 13th Int'l Conf. on Parallel and Distributed Computing Systems (PDCS-2000.

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