On 3/8/06, Piotras <pp@info...> wrote:
> However , many times I am logged in as SG0 admin ( using basic auth)
> and I create objects and set their sitegroup later.
> Just because I can not open and close my browser every one minute.
> ( which of course proves that one admin host per sg is a good thing )
How about if a new object inherited the parent objects sitegroup by
default. That would take care of a lot of problems. Something like
1) If user is in SGn (n > 0), create object in SGn
2) If parent object is in SGx (x >= 0), create object in SGx
3) If sitegroup property is set to SGx (x >= 0), create object in SGx
4) Otherwise create object in SG0
The first rule takes care of all normal usage, the rest would cover
administrative tools like Aegir when using SG0. The order of rules 2
and 3 is debatable, but I think this order is better because its
better in avoiding potential database inconsistencies.
To be really safe we'd add checks to outlaw cross-sitegroup parent and
other links, but that's probably too much to ask. :-)