Reader/writer terminology

Before you copy paste this into the docs you are writing:

In the current implementation of the
daemon any interaction (send or query) with a machine makes the daemon
a follower for that machine unless it is not already the owner.

I’m fine with the terminology change.

James

···

On Thu, Feb 7, 2019 at 3:17 PM Thomas Scholtes thomas@monadic.xyz wrote:

Hey everybody,

I’m working on the concepts and terminology documentation for the

release. I’m not quite satisfied with the “reader”/“writer” terminology

we use when describing machines and the daemon.

I propose to get rid of those terms and replace them with “owner” and

“follower”.

A Radicle daemon instance owns a machine if it can change the IPNS

name for the machine. That is it has access to the IPFS daemon that

holds the IPNS key. Conversely the owner of a Radicle machine is the

instance that can change the IPNS name. The owner of a Radicle machine

accepts inputs to the machine from the network, applies them, and

updates the machine’s input log.

A Radicle daemon follows a machine if it materializes the machine

state in memory and replicates the machine’s input log. Following a

machine means that we poll for updates to the IPNS name and (almost)

always have the latest state. In the current implementation of the

daemon any interaction (send or query) with a machine makes the daemon

a follower for that machine unless it is not the owner.

I like this a lot : )

···

On Thu, Feb 7, 2019 at 4:26 PM James Haydon james@monadic.xyz wrote:

Before you copy paste this into the docs you are writing:

In the current implementation of the
daemon any interaction (send or query) with a machine makes the daemon
a follower for that machine unless it is not already the owner.

I’m fine with the terminology change.

James

On Thu, Feb 7, 2019 at 3:17 PM Thomas Scholtes thomas@monadic.xyz wrote:

Hey everybody,

I’m working on the concepts and terminology documentation for the

release. I’m not quite satisfied with the “reader”/“writer” terminology

we use when describing machines and the daemon.

I propose to get rid of those terms and replace them with “owner” and

“follower”.

A Radicle daemon instance owns a machine if it can change the IPNS

name for the machine. That is it has access to the IPFS daemon that

holds the IPNS key. Conversely the owner of a Radicle machine is the

instance that can change the IPNS name. The owner of a Radicle machine

accepts inputs to the machine from the network, applies them, and

updates the machine’s input log.

A Radicle daemon follows a machine if it materializes the machine

state in memory and replicates the machine’s input log. Following a

machine means that we poll for updates to the IPNS name and (almost)

always have the latest state. In the current implementation of the

daemon any interaction (send or query) with a machine makes the daemon

a follower for that machine unless it is not the owner.

Hey everybody,

I’m working on the concepts and terminology documentation for the
release. I’m not quite satisfied with the “reader”/“writer” terminology
we use when describing machines and the daemon.

I propose to get rid of those terms and replace them with “owner” and
“follower”.

A Radicle daemon instance *owns* a machine if it can change the IPNS
name for the machine. That is it has access to the IPFS daemon that
holds the IPNS key. Conversely the *owner* of a Radicle machine is the
instance that can change the IPNS name. The owner of a Radicle machine
accepts inputs to the machine from the network, applies them, and
updates the machine’s input log.

A Radicle daemon *follows* a machine if it materializes the machine
state in memory and replicates the machine’s input log. Following a
machine means that we poll for updates to the IPNS name and (almost)
always have the latest state. In the current implementation of the
daemon any interaction (send or query) with a machine makes the daemon
a follower for that machine unless it is not the owner.

+1 here too.

···

On Thu, Feb 7, 2019 at 5:15 PM Alexis Sellier alexis@monadic.xyz wrote:

I like this a lot : )

On Thu, Feb 7, 2019 at 4:26 PM James Haydon james@monadic.xyz wrote:

Before you copy paste this into the docs you are writing:

In the current implementation of the
daemon any interaction (send or query) with a machine makes the daemon
a follower for that machine unless it is not already the owner.

I’m fine with the terminology change.

James

On Thu, Feb 7, 2019 at 3:17 PM Thomas Scholtes thomas@monadic.xyz wrote:

Hey everybody,

I’m working on the concepts and terminology documentation for the

release. I’m not quite satisfied with the “reader”/“writer” terminology

we use when describing machines and the daemon.

I propose to get rid of those terms and replace them with “owner” and

“follower”.

A Radicle daemon instance owns a machine if it can change the IPNS

name for the machine. That is it has access to the IPFS daemon that

holds the IPNS key. Conversely the owner of a Radicle machine is the

instance that can change the IPNS name. The owner of a Radicle machine

accepts inputs to the machine from the network, applies them, and

updates the machine’s input log.

A Radicle daemon follows a machine if it materializes the machine

state in memory and replicates the machine’s input log. Following a

machine means that we poll for updates to the IPNS name and (almost)

always have the latest state. In the current implementation of the

daemon any interaction (send or query) with a machine makes the daemon

a follower for that machine unless it is not the owner.