From: Klanjabrik - <klanjabrik@gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Heads up: protocol changes for Galene 0.5
Date: Sun, 30 Jan 2022 05:49:12 +0700 [thread overview]
Message-ID: <CAC0ND9wbMqqacFWEuz8vVfJpX=SX0ne9vrASk=Ht34GKZj9AjA@mail.gmail.com> (raw)
In-Reply-To: <87wniijhak.wl-jch@irif.fr>
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
Thanks for the update.
On Sun, Jan 30, 2022, 05:42 Juliusz Chroboczek <jch@irif.fr> wrote:
> Some minor protocol changes. Rationale at the end.
>
> 1. What was previously known as "user.status" is now known as "user.data".
> The userAction "setstatus" is now known as "setdata".
>
> We now consistently distuinguish between "status", which is maintained by
> the server, and "data", which is controlled by the client.
>
>
> 2. The "user.data" may be set at the time of joining a group.
>
> Previously, one needed to join a group and then set "user.data". It is
> now possible to set "user.data" at the time of joining, which avoids the
> need to debounce "user" messages.
>
>
> 3. We now implement "group.data" in addition to "user.data" and
> "group.status".
>
> Group.data may be set by any group operator, and is propagated to all
> clients in a group by the means of "joined" messages. If you're using
> protocol.js, it's a parameter of the "onjoined" callback.
>
>
> # Rationale
>
> Anabole.com have been forking Galene for remote teaching of primary school
> students. My goal with these changes is to ensure that they only modify
> the client, and that they don't need to make any changes to the server.
>
> In their user interface, they store a user avatar's position in the
> "user.data" field; if the "user.data" field cannot be set at joining time,
> the other clients receive two "user" notifications, which leads to display
> flicke.r
>
> Another feature is to allow the teacher to set the current exercice
> number, and have it prominently displayed for all students. This is
> currently done using ad-hoc userMessages, which is racy; the goal is to
> store it in "group.data".
>
> -- Juliusz
> _______________________________________________
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org
>
[-- Attachment #2: Type: text/html, Size: 2649 bytes --]
prev parent reply other threads:[~2022-01-29 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 22:41 [Galene] " Juliusz Chroboczek
2022-01-29 22:49 ` Klanjabrik - [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC0ND9wbMqqacFWEuz8vVfJpX=SX0ne9vrASk=Ht34GKZj9AjA@mail.gmail.com' \
--to=klanjabrik@gmail.com \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
--subject='[Galene] Re: Heads up: protocol changes for Galene 0.5' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox