From 4e26f3d740e2942b9c101a45dfb6498fa1bbc9ce Mon Sep 17 00:00:00 2001 From: Oskar Thoren Date: Wed, 2 Oct 2019 14:44:22 +0800 Subject: [PATCH] explain spike --- _posts/2019-10-01-remote-log.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2019-10-01-remote-log.md b/_posts/2019-10-01-remote-log.md index 5c263ef..9f5a58a 100644 --- a/_posts/2019-10-01-remote-log.md +++ b/_posts/2019-10-01-remote-log.md @@ -31,7 +31,7 @@ In this post we are going to describe how such a remote log schema could work. S A remote log is a replication of a local log. This means a node can read data from a node that is offline. -The spec is in an early draft stage and can be found [here](https://github.com/vacp2p/specs/pull/16). A very basic spike can be found [here](https://github.com/vacp2p/research/tree/master/remote_log). The rest of this post follows the current spec closely. +The spec is in an early draft stage and can be found [here](https://github.com/vacp2p/specs/pull/16). A very basic [spike](https://en.wikipedia.org/wiki/Spike_(software_development))/proof-of-concept can be found [here](https://github.com/vacp2p/research/tree/master/remote_log). The rest of this post follows the current spec closely. ### Definitions