From: Juliusz Chroboczek <jch@irif.fr>
To: Dianne Skoll <dianne@skoll.ca>
Cc: galene@lists.galene.org
Subject: [Galene] Re: API versioning (was Re: Re: API documentation)
Date: Thu, 11 Apr 2024 14:55:01 +0200 [thread overview]
Message-ID: <87zfu0awka.wl-jch@irif.fr> (raw)
In-Reply-To: <171279372600.1000.262671797887854827@gauss.local>
>> The /0/ is intriguing,
> It was I who suggested a versioned API.
Yep, credit where credit's due.
> the cost of doing it and not needing it is small, whereas the cost of
> not doing it and then discovering it is needed is large.
To be fair, even if we don't version the API at the outset, we could
always switch to /galene-api-v42/.groups/ or to /galene-api/.groups-v42/.
But, as you say, the cost is just two bytes per request.
-- Juliusz
prev parent reply other threads:[~2024-04-11 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 19:40 [Galene] API documentation Juliusz Chroboczek
2024-04-10 20:47 ` [Galene] " Gabriel Kerneis
2024-04-10 23:09 ` Juliusz Chroboczek
2024-04-11 0:02 ` [Galene] API versioning (was Re: Re: API documentation) Dianne Skoll
[not found] ` <171279372600.1000.262671797887854827@gauss.local>
2024-04-11 12:55 ` Juliusz Chroboczek [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=87zfu0awka.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