Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Dianne Skoll <dianne@skoll.ca>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Galene API frozen?
Date: Thu, 02 May 2024 22:33:01 +0200	[thread overview]
Message-ID: <87a5l8vts2.wl-jch@irif.fr> (raw)
In-Reply-To: <171468106125.1473.12323438012415538261@gauss.local>

>>> rather than returning plain-text, one-per-line, wouldn't it make
>>> more sense to return a JSON array?

>> No objection if people feel strongly that way, but what's the
>> advantage?

> Consistency.

I think there's a stronger argument.

Galene group names may contain any character including newlines.  So
I need to either forbid newlines in Galene group names, or define
a quoting mechanism.  And JSON comes bundled with its own quoting
mechanism...

I'll think it over.

> The usual way to handle this case is to provide a paged API

...and run into all sorts of issues with atomicity.

-- Juliusz

  parent reply	other threads:[~2024-05-02 20:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 17:32 [Galene] Galene API frozen? Juliusz Chroboczek
2024-05-02 19:22 ` [Galene] " Dianne Skoll
     [not found] ` <171467774184.1473.5473206404325247014@gauss.local>
2024-05-02 20:07   ` Juliusz Chroboczek
2024-05-02 20:17     ` Dianne Skoll
     [not found]     ` <171468106125.1473.12323438012415538261@gauss.local>
2024-05-02 20:33       ` Juliusz Chroboczek [this message]
2024-05-02 20:53         ` Dianne Skoll
2024-05-03 18:26   ` Juliusz Chroboczek

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=87a5l8vts2.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=dianne@skoll.ca \
    --cc=galene@lists.galene.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox