From 1dacff78d89960f0f8d239eaf2de96562a5b4114 Mon Sep 17 00:00:00 2001 From: adnkhn Date: Sun, 9 Sep 2012 05:11:32 -0700 Subject: [PATCH] Updated _posts/features/0100-01-03-distributed.md --- _posts/features/0100-01-03-distributed.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/features/0100-01-03-distributed.md b/_posts/features/0100-01-03-distributed.md index 032da14d5..bd776fa63 100644 --- a/_posts/features/0100-01-03-distributed.md +++ b/_posts/features/0100-01-03-distributed.md @@ -12,7 +12,7 @@ categories: published: true --- -Substance is being designed as a distributed system. Every peer can act as a server or client. Nodes can either run locally on your computer or somwhere on the web. It's the same piece of software, except that public nodes may use more sophisticated backends as they most likely need to scale. +Substance is totally being designed as a distributed system. Every peer can act as a server or client. Nodes can either run locally on your computer or somwhere on the web. It's the same piece of software, except that public nodes may use more sophisticated backends as they most likely need to scale. With Substance our goal is the provision of a modern technology stack, enabling collaborative document composition in realtime between multiple peers. The system is split into separate modules, which talk to each other using message passing. So our System is all about exchanging and manipulating digital documents over the network. To ensure all parties can communicate fluently, we defined a common vocabulary that is spoken by all parties, the [Substance Document Protocol](/modules/document.html). @@ -75,4 +75,4 @@ Let's walk through a simple example: 1. Well, now `John` has a fresh document. 1. Some time later `Paul` joins the party. He also connects to that server. 1. `Paul` opens the document just created by `John`. The server is aware that there's an active document session so John just joins that session and as a response gets the current state of the document. -1. `Paul` just adds an image at the bottom of the document then, which triggers an operation `node:insert` broadcasted to all active clients, in our case `John`. Under the hood the document session is aware of clients participating in a session and sends distributes messages accordingly. For every session a document instance is kept in memory, which gets transformed as operations come in. +1. `Paul` just adds an image at the bottom of the document then, which triggers an operation `node:insert` broadcasted to all active clients, in our case `John`. Under the hood the document session is aware of clients participating in a session and sends distributes messages accordingly. For every session a document instance is kept in memory, which gets transformed as operations come in. \ No newline at end of file