Bayeux: an architecture for scalable and fault-tolerant wide-area data dissemination
By Shelley Zhuang, Ben Y. Zhao, Anthony D. Joseph, Randy Howard Katz, John D. Kubiatowicz. International Workshop on Network and Operating System Support for Digital Audio and Video, 2001
885 citations recorded by the source corpus.
Subfields: Computer Networks and Communications
View Paper: https://www.semanticscholar.org/paper/1af95c54c7fb2f6eec6040cf3a8191860726778c
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Computer Networks and Communications
- Peter Druschel
- Anne-Marie Kermarrec
- Antony Ian Taylor Rowstron
- John Risson
- Tim Moors
- Miguel Oom Temudo de Castro
- John D. Kubiatowicz
- Ion Stoica
Citations in the corpus
- Opportunities and Challenges of Peer-to-Peer Internet Video Broadcast (2008, background): “A large number of proposals have emerged in recent years for peer-to-peer video broadcast [4]–[6], [8], [9], [14], [16], [19], [22], [27]–[29], [36], [37], [41], [43].”
- CoolStreaming/DONet: a data-driven overlay network for peer-to-peer live media streaming (2005, background): “In the former, a set of servers or application-level proxies are strategically placed, and a high-quality overlay can then be constructed with the assistance of these anchor nodes [1], [2], [24], [26], [28].”
- Towards a Common API for Structured Peer-to-Peer Overlays (2003, background): “Structured overlays can be used to construct services such as distributed hash tables [4], scalable group multicast/anycast [3, 12], and decentralized object location [5].”
- Meghdoot: Content-Based Publish/Subscribe over P2P Networks (2004, methodology): “Bayeux [31] uses Tapestry [30] as the underlying structure.”
- Peer-to-Peer Membership Management for Gossip-Based Protocols (2003, background): “Recently, a class of decentralized application-level protocols relying on peerto-peer generic object location and routing substrates have emerged ([6], [27], [23]).”
- Tapestry: a resilient global-scale overlay for service deployment (2004, neutral): “Several systems have application level multicast: CAN-MC [21] (CAN), Scribe [22] (Pastry), and Bayeux [5] (Tapestry).”
- Resilient peer-to-peer streaming (2003, background): “Recent work has leveraged the scalable routing substrate provided by distributed hash tables (DHTs) to build efficient multicast trees (e.g., Bayeux [ 38 ], Scribe [12]).”
- DONet: A Data-Driven Overlay Network For Efficient Live Media Streaming (2004, background): “Such a 2We decide to use two different names: DONet and CoolStreaming, because the former is technically sound and the latter is ”commercially” sound – currently, a majority of CoolStreaming users are non-networking researchers, or even non-researchers.”
- Enabling conferencing applications on the internet using an overlay muilticast architecture (2001, background): “Gossamer [2], Narada [3], Yoid [6] and most recently, Bayeux [ 13 ], have only considered delay based metrics.”
- The many faces of publish/subscribe (2003, methodology): “2002; Banerjee et al. 2002; Ratnasamy et al. 2001; Zhuang et al. 2001] are commonly employed.”
- Distributing streaming media content using cooperative networking (2002, methodology): “A multicast distribution tree can be constructed using reverse-path forwarding (as in systems such as Bayeux [31] and Scribe [23]).”
- Cooperative peer groups in NICE (2003, background): “This situation is not unique to Chord; all hash-based location systems, including CAN [11], Bayeux [17], Pastry [13], have this property.”
- Graph-theoretic analysis of structured peer-to-peer systems: routing distances and fault resilience (2003, background): “Many current DHTs [17], [35], [37], [43], [44] rely on the”
- A survey and comparison of peer-to-peer overlay network schemes (2005, background): “Peer s is the i th finger of peer n ( n.”
- OpenDHT: a public DHT service and its uses (2005, neutral): “As described in Section 4, existing DHT-based multicast systems [7, 27, 35] typically use a routing interface.”