From 0d8c3518c400e0b50243677ba55a89d5d8c4a75c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alexis=20M=C3=A9taireau?= Date: Sat, 11 Nov 2023 22:26:42 +0100 Subject: [PATCH] Update documentation --- ...time-collaboration-to-umap-first-week.html | 22 +++++++++++++------ 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/drafts/adding-real-time-collaboration-to-umap-first-week.html b/drafts/adding-real-time-collaboration-to-umap-first-week.html index d2b822e..71952bc 100644 --- a/drafts/adding-real-time-collaboration-to-umap-first-week.html +++ b/drafts/adding-real-time-collaboration-to-umap-first-week.html @@ -97,7 +97,7 @@ the current code base.

  • The server is here mainly to handle access rights, store the data and send it over to the clients.
  • The actual rendering and modifications of the map are directly done in JavaScript, on the clients.
    • -

    The data is split in multiple layers. At the time of writing, concurrent writes to the same layers are not possible, as one edit would potentially overwrite the other one. It’s possible to have concurrent edits on different layers, though.

    +

    The data is split in multiple layers. At the time of writing, concurrent writes to the same layers are not possible, as one edit would potentially overwrite the other. It’s possible to have concurrent edits on different layers, though.

    When a change occurs, each DataLayer is sent by the client to the server.