mirror of
https://code.briarproject.org/briar/briar.git
synced 2026-02-25 17:18:17 +01:00
akwizgran created page: ForumApp
@@ -1,8 +1,8 @@
|
|||||||
BSP is an application layer data synchronisation protocol for delay-tolerant networks. It can operate over any transport that can deliver a simplex stream of bytes from a sender to a recipient on a best-effort basis, meaning that streams may be delayed, lost, reordered or duplicated by the transport. BSP does not ensure the confidentiality, authenticity or integrity of streams; that is the responsibility of a transport layer security protocol such as [BTP](BTP).
|
BSP is an application layer data synchronisation protocol for delay-tolerant networks. It can operate over any transport that can deliver a simplex stream of bytes from a sender to a recipient on a best-effort basis, meaning that streams may be delayed, lost, reordered or duplicated by the transport. BSP does not ensure the confidentiality, authenticity or integrity of streams; that is the responsibility of a transport layer security protocol such as [BTP](BTP).
|
||||||
|
|
||||||
BSP synchronises data between two devices referred to as the local and remote peers. The data to be synchronised consists of messages, which are organised into channels. From BSP's point of view, a message is simply a sequence of bytes and a channel is simply a set of messages.
|
BSP synchronises data between two devices referred to as the local and remote peers. The data to be synchronised consists of messages, which are organised into channels. From BSP's point of view, a message is simply a sequence of bytes and a channel is simply a set of messages. A message created by the local peer is called a local message, while a message synchronised from the remote peer is called a remote message.
|
||||||
|
|
||||||
Each channel on the local peer belongs to an application, which is responsible for deciding which messages are valid (the validity policy), which messages should be stored on the local peer (the storage policy), and which messages should be shared with the remote peer (the sharing policy).
|
Each channel on the local peer belongs to an application, which is responsible for deciding which messages are valid (the validity policy), which remote messages should be stored on the local peer (the storage policy), and which local messages should be shared with the remote peer (the sharing policy).
|
||||||
|
|
||||||
### Notation
|
### Notation
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user