Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <>
To: Han So <>
Subject: [Galene] Re: Federated servers or multiple turns?
Date: Thu, 24 Nov 2022 20:59:57 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> Had anyone worked on federating multiple Galene servers

The original plan was to allow server federation, and to allow
distributing a single group on multiple servers.  It turned out, however,
that Galene requires fewer server ressources than initially expected, so
the need for such fine-grained load-balancing didn't materalise.

For now, you can distribute load by putting different Galene groups on
different servers.  You may either redirect clients to the right server at
the HTTP level (see the "redirect" directive in the configuration file),
or you could redirect just the websocket connection (so the URL visible in
the browser is the one of the original server, not the one that that the
user has been redirected to).

> having multiple turn servers?

You could have multiple TURN servers, sure.  Could you please explain why
you'd want that?

-- Juliusz

  reply	other threads:[~2022-11-24 19:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 16:43 [Galene] " Han So
2022-11-24 19:59 ` Juliusz Chroboczek [this message]
2022-11-30 15:11   ` [Galene] " Han So
2022-11-30 15:33     ` Dave Taht
2022-11-30 23:06     ` Juliusz Chroboczek
2022-12-02  3:08       ` Han So
2022-12-02 11:39         ` Juliusz Chroboczek
2022-12-05 16:38           ` Han So
2022-12-05 17:14             ` Han So
2022-12-05 22:03               ` Han So
2022-12-06 18:21                 ` Han So
2022-12-07 15:17                   ` Han So

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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