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

[Juliusz Chroboczek <jch@irif.fr>]

>> 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.

> That sort of works - but we ended up (perhaps shooting ourselves in the
> foot) by also configuring auth, presenters, if it could, or could not,
> get recorded, etc.

I see.

>> 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?

> Not too worried about that - very easy to do with a DELETE from the
> configuration service once every night or so.

Ok.

> So conceivably - the API with subgroups may works if you accept that you
> get no 'callback' from Galene telling you that a new group was created
> (and we set them to private - so no polling of the public-public.json).

If you have an auth token, you can check if a group exists simply by doing
HEAD to /galene-api/group/whatever/.  No objection to implementing
a callback, though, if for some reason you cannot poll the server.

-- Juliusz