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

[Dirk-Willem van Gulik <dirkx@webweaving.org>]

I've been using a bit of a hack in 

	group/Update)
		https://github.com/jech/galene/blob/0f53bf037368a2a82a0af30ffd07bf5943b0abb1/group/group.go#L1335

and especially
	group/GetDescription()
		https://github.com/jech/galene/blob/0f53bf037368a2a82a0af30ffd07bf5943b0abb1/group/group.go#L1007

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. 

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

And this http/rev-proxy separation also makes it easier to limit the access galene has; much like the galene-ldap separation/pattern.

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

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

With kind regards,

Dw