mirror of https://github.com/acid-info/vac.dev.git
tweaks
This commit is contained in:
parent
adf83469d4
commit
33266f1b67
|
@ -1,18 +1,16 @@
|
||||||
---
|
---
|
||||||
layout: post
|
layout: post
|
||||||
name: "Remote log data sync"
|
name: "Remote log"
|
||||||
title: "Remote log data sync"
|
title: "P2P Data Sync with a Remote Log"
|
||||||
date: 2019-10-04 12:00:00 +0800
|
date: 2019-10-01 12:00:00 +0800
|
||||||
author: oskarth
|
author: oskarth
|
||||||
published: false
|
published: true
|
||||||
permalink: /remote-log
|
permalink: /remote-log
|
||||||
categories: research
|
categories: research
|
||||||
summary: A research log. Reliable and decentralized, pick two.
|
summary: A research log. Reliable and decentralized, pick two.
|
||||||
image: /assets/img/remote_log.png
|
image: /assets/img/remote_log.png
|
||||||
---
|
---
|
||||||
|
|
||||||
## Introduction
|
|
||||||
|
|
||||||
A big problem when doing end-to-end data sync between mobile nodes is that most
|
A big problem when doing end-to-end data sync between mobile nodes is that most
|
||||||
devices are offline most of the time. With a naive approach, you quickly run
|
devices are offline most of the time. With a naive approach, you quickly run
|
||||||
into issues of 'ping-pong' behavior, where messages have to be constantly
|
into issues of 'ping-pong' behavior, where messages have to be constantly
|
||||||
|
@ -165,7 +163,7 @@ The *remote log* protobuf is what is stored at the Name system.
|
||||||
<!-- diagram -->
|
<!-- diagram -->
|
||||||
|
|
||||||
<p align="center">
|
<p align="center">
|
||||||
<img src="./remote-log.png" />
|
<img src="{{site.baseurl}}/assets/img/remote-log.png">
|
||||||
<br />
|
<br />
|
||||||
Figure 1: Remote log data synchronization.
|
Figure 1: Remote log data synchronization.
|
||||||
</p>
|
</p>
|
||||||
|
|
Binary file not shown.
After Width: | Height: | Size: 17 KiB |
Loading…
Reference in New Issue