[Kroupware] Web interface frontend

[Andreas Jellinghaus]

brad, i think you misunderstood me.

the user has nothing to do with this,
its pure internal details. the admin will
have to understand it, but the user will
never have to see them, no matter how it is done.

i think we can agree, that there are several good ways
to make the user happy, make their live easier, such as
 - good wizards
 - step by step instructions, easy to understand
 - pre configuration (quite easy to do in company systems)
 - ...

after all most users are not computer experts and there
is no reason they should be. right?

the details of easy configuration for the users are
dns with svr records versus slp records, or how some
wizard or configuration tool internaly works. 

i wasn't writing about that.

what i am concerned is the complexity of the whole system
as the administrator has to understand it, in order to debug
and solve problems.

and i think the dns approach (user_at_company_com.mail.company.com)
has no benefits compared with two stage systems (first stage
round-robin/load balancer and proxy, second stage storage server).

for example, dns is cached. now how do you want to move a user mailbox
from one server to some other? the first stage could block / return an
info mail, while some machine works on the secondary server). but with
dns? either disable caching, or face half filled inboxes.

also i wonder how the whole virtual domain setup (_at_company_com / 
_at_other_com) mixes with shared folders like shared.info.general ?
can anyone suggest how that will work?

regards, andreas