[Galene] Re: Virtual groups v.s. new API branch

[Juliusz Chroboczek <jch@irif.fr>]

> to be able to have the /var/db/galene/groups directory (i.e. the -groups
> cmd line argument) live on a nearby webserver. Basically it just fetches
> the JSON remote every time.

Right, makes sense.

> The main reason for this is to allow the ad-hoc creation of short lived
> ephemeral rooms that you discover you need, rather than
> preconfigured. (the jsons are generated on the fly in typical 'cgi-bin'
> conceptual fashion).

We use the "allow-subgroups" mechanism for that.  We create a template
group with "allow-subgroups" set to true, and subgroups are created on the
fly when a user joins.

I'm not opposed to hosting group definitions on a remote server, but I'd
need to understand why the existing mechanism does not meet your use case.

> Now I just noticed this https://github.com/jech/galene/tree/api. Fair to
> assume that this will be the `proper' way ?

That's the plan, but it's still open to discussion.  In order to create
a group, you'll do:

    PUT /galene-api/group/groupname/ HTTP/1.1
    If-None-Match: *
    Content-Type: application/json

with the group definition in the body.  Perhaps it's worth adding
"not-before" and "expires" fields to the group definition, and have groups
be automatically purged by the server?

> Or is there also a plan for a more 'reactive' mechanism -- i.e. one that
> does not require a configuration sitting pretty `ahead' of time. We're
> finding this quite useful (and then lock the room one we're started).

I'm not opposed, but I'd need to understand why the "allow-subgroups"
mechanism is not good enough for your use case.

-- Juliusz