| Birrell, A. D., Levin, R., Needham, R.M. and Schroeder, M. D. Grapevine: An exercise in distributed computing. Comm. ACM 25, 4 (Apr. 1982), 260-274. |
....however, is quite challenging, because the name space of a location independent name usually tends to be flat and not scalable. In order to design a scalable location independent naming system, scalable name space and efficient name management resolution algorithms are desired. The Grapevine [4] proposed by XEROX PARC is one of the earliest locationindependent naming systems; it utilizes hierarchical name space, and enables users to locate persons or equipment in an office environment. The X.500 directory service [5] which works on the current Internet, enables users to locate various ....
A. Birrell, R. Levin, R. Needham, and M. Schroeder, "Grapevine: An Exercise in Distributed Computing", Communications of the ACM, Vol. 25, No. 4, Apr. 1982.
....anti entropy protocol [12] These systems suffer from the same scalability problems, limiting scale to perhaps a few thousands of participants. Also influential to the design of Astrolabe is Butler Lampson s paper on the design of a global name service [16] based on experience with Grapevine [7] and Clearinghouse. This paper enumerates the requirements of a name service, which include large size, high availability, fault isolation, and tolerance of mistrust, all of which we believe Astrolabe supports. The paper s design does not include aggregation, but otherwise shares many of the ....
A. Birrell, R. Levin, R. Needham, and M. Schroeder. Grapevine: an exercise in distributed computing. CACM, 25(4):260--274, April 1982.
....resource properties, expressiveness offered by their look up interfaces, whether they offer push based or pullbased discovery and whether queries are mediated by a directory service or resolved in a peer to peer fashion in the system. In addition to the classical examples like Grapevine, GNS [19] and X.500 [20] a range of industrial standards like Microsoft s UPnP resource discovery protocol (SSDP) 11] IBM s T Spaces, and IETF s Service Location Protocol [9] and experimental systems like MIT s INS [4] and Berkeley s SSDS [3] have emerged over the last few years. For example, where SLP ....
A. Birrell et al. Grapevine: An exercise in distributed computing. Comm. Of the ACM, 25(4):260--274, April 1982.
....For those publishers given names, the name describes a path from the root to a leaf in the tree. For example, a temperature sensor in Sudikoff room 215 might be named [ Sudikoff 2F 215 temp sensor ] To enhance scalability, multiple levels of naming may be helpful; although many examples exist [25, 4], perhaps the most common example is the two level name (hostname: filename) used in URLs. The name space may be less structured. Each named publisher could be given a set of descriptive attribute value pairs [2, 18] The above temperature sensor might be named [sensor=temperature, room=215, ....
A. D. Birrell, R. Levin, R. M. Needham, and M. D. Schroeder. Grapevine: An exercise in distributed computing. Communication of ACM, 25(4):260--274, April 1982.
....attribute based information on a variety of objects but, generally, without supporting complicated transactions or roll back schemes as those found in traditional database management systems. However, none support the ability to proactively notify clients of updates as in PDS. Grapevine [12] and Global Name Service [80] were two pioneering distributed directory services. Other more recent services such as DNS [87] and the X.500 Directory Service [112] provide such services under the assumption of fairly stable mappings between objects attributes and their values. Such an assumption ....
Andrew Birrell, Roy Levin, Roger M. Needham, and Michael D. Schroeder. Grapevine: An exercise in distributed computing. Communication of the ACM, 25(4):260-274, April 1982.
....does not wait for the Write to propagate to other servers. In other words, Bayou presents a weakly consistent replicanon model with a read any write any style of access. Weakly consistent replication has been used previously for availability, simplicity and scalability in a variety of systems [3, 7, 10, 12, 15, 19]. 173 boundades Anti entropy Read Figure 1. Bayou System Model While individual Read and Write operations are performed at a single server, clients need not confine themselves to interacting with a single server. Indeed, in a mobile computing environment, switching between servers is often ....
A. Birrell, R. Levin, R. M. Needham, and M.D. Schroeder. Grapevine: An exercise in distributed computing. Communications of the ACM 25(4):260-274, April 1982.
....such as Orca [3] allows operations to be re ordered as long as they remain consistent with the view of individual clients. An inherent disparity in the performance of atomic and sequentially consistent objects has been established [2] Other systems provide even weaker guarantees to the clients [6, 5, 7] in order to get better performance. Improving performance by providing weaker guarantees results in more complicated semantics. Even when the behavior of the replicated objects is specified unambiguously, it is more difficult to understand and to reason about the correctness of implementations. ....
....and implementing directory services. In a distributed computing enterprise, naming and directory are impor tant and basic services used to make distributed re sources accessible transparently to the locations or the physical addresses of users and resources. Such ser vices include Grapevine [5], DECdns [14] DCE GDS (Global Directory Service) and CDS (Cell Directory Service) 19] ISO OSI X.500 [11] and the Internet s DNS (Domain Name System) 10] A directory service must be robust and it must have good response time for name lookup and translation requests in a geographically ....
A. Birrell, R. Levin, R. Needham, and M. Schroeder. Grapevine: An exercise in distributed computing. Com- munications of the ACM, 25(4):260-274, 1982.
....however, that the user is available for help and users may feel the applications are intrusive and become reluctant to use them. 6. 5 Naming systems Solar allows publishers and services to be identified by context sensitive names (CSN) Most other distributed naming systems, like Grapevine [6] and the Global Naming Service [24] assume name bindings are mostly static. Unix symbolic links allow for aliasing as in Solar, but they are largely static, and there is no automatic way to learn about binding changes. Plan 9 [31] uses a file system interface to represent a wide range of ....
Andrew D. Birrell, Roy Levin, Roger M. Needham, and Michael D. Schroeder. Grapevine: An exercise in distributed computing. Communication of ACM, 25(4):260--274, April 1982.
No context found.
Birrell, A. D., Levin, R., Needham, R.M. and Schroeder, M. D. Grapevine: An exercise in distributed computing. Comm. ACM 25, 4 (Apr. 1982), 260-274.
No context found.
Birrell, A. D., Levin, R., Needham, R.M. and Schroeder, M. D. Grapevine: An exercise in distributed computing. Comm. ACM 25, 4 (Apr. 1982), 260-274.
....ANDREW Do BIRRELL, and ROGER M. NEEDHAM Xerox Palo Alto Research Center Grapevine is a distributed, replicated system that provides message delivery, naming, authentication, resource location, and access control services in an internet of computers. The system, described in a previous paper [1], was designed and implemented several years ago. We now have had operational experience with the system under substantial load. In this paper we report on what we have learned from using Grapevine. Categories and Subject Descriptors: C.2.4 [Computer Communication Networks] Distributed ....
....Reliability Additional Key Words and Phrases: Grapevine 1. INTRODUCTION Grapevine is a distributed, replicated system that provides message delivery, naming, authentication, resource location, and access control services in an internet of computers. The system, described in a previous paper [1], was designed and implemented several years ago. Operational experience with the system under substantial load has proved the original design sound in most aspects, although there have been some surprises. In this paper we report on what we have learned from using Grapevine. Our experience may ....
[Article contains additional citation context not shown here]
BIRRELL, A.D., LEVIN, R., NEEDHAM, R.M., AND SCHROEDER, M.D. Grapevine: an exercise in distributed computing. Commun. ACM 25, 4 (April 1982), 260-274.
No context found.
Andrew D. Birrell, Roy Levin, Roger M. Needham, and Michael D. Schroeder. Grapevine: An exercise in distributed computing. Communications of the ACM, 25(4):260--274, April 1982.
No context found.
Birrell, A., Levin, R., Needham, R., and Schroeder, M., "Grapevine: An Exercise in Distributed Computing",Comm ACM 25, 4 (April 1982), 260-274.
No context found.
A. D. Birrell, R. Levin, R. M. Needham, and M. D. Schroeder. Grapevine: An exercise in distributed computing. Communications of the ACM, 25(4):260--274, Apr. 1982.
No context found.
Andrew D. Birrell, Roy Levin, Roger M. Needham, and Michael D. Schroeder. Grapevine: An exercise in distributed computing. Communications of the ACM, 25(4):260--274, April 1982.
No context found.
Andrew D. Birrell, Roy Levin, Roger M. Needham, and Michael D. Schroeder. Grapevine: An exercise in distributed computing. Communications of the ACM, 25(4):260--274, April 1982.
No context found.
Andrew D. Birrell, Roy Levin, Roger M. Needham, and Michael D. Schroeder. Grapevine: An exercise in distributed computing. Communications of the ACM, 25(4):260--274, April 1982.
No context found.
A.D. Birrell, R. Levin, R.M. Needham, and M.D. Schroeder. Grapevine: an exercise in distributed computing. Communications of the ACM, 25(4):260--274, 1982.
No context found.
Birrell, A., Levin, R., Needham, R., and Schroeder, M., "Grapevine: An Exercise in Distributed Computing",Comm ACM 25, 4 (April 1982), 260-274.
No context found.
Andrew D. Birrell, Roy Levin, Roger M. Needham, and Michael D. Schroeder. Grapevine: An exercise in distributed computing. Communications of the ACM, 25(4):260--274, April 1982. 36.
No context found.
A. D. Birrell et al. Grapevine: an exercise in distributed computing. Communications of the ACM 25(4):260-274, April, 1982.
No context found.
Birrell, A., Levin, R., Needham, R. M., and Schroeder, M. D. Grapevine: An exercise in distributed computing. Communications of the ACM. Apr 1982.
No context found.
A. Birrell, R. Levin, R. Needham, and M. Schroeder. Grapevine: an exercise in distributed computing. Communications of the ACM, 25(4):260--274, April 1982.
No context found.
A. Birrell, R. Levin, R. Needham, and M. Schroeder. Grapevine: An Exercise in Distributed Computing. Communications of the ACM, 25(4):260-274, 1982.
No context found.
A. D. Birrell, R. Levin, R. M. Needham and M. D. Schroeder, `Grapevine: an exercise in distributed computing', Communications of the ACM, 25, (4), 260--274 (1982).
First 50 documents Next 50
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