[Typo3-dev] Re: The future of typo3

[Jan-Hendrik Heuing [netfielders]]

>>All the "bridges" between front end and
>>back end users (front end user - to back end user mapping, backend login
>>in front end and so on) are symptoms of poor design.
>
>Right.
>
>Mixing frontend and backend users are symptoms of a poor design as well, a
design I wouldn't use >if I had a very important website to run.
>I once studied electronics. There you have various devices to transmit
signals with "hermitical >separation". Why? To make sure that the risk of
error is very very low under extreme unforeseem >conditions.
>The same here: Having two user tables in design provides a safer system.

I've been following this, and I hardly find any time for it. Most of my
thoughts have been  said by others. One thing this I am still interested in:

You (Michael) say that not seperating fe-be-users is better design. I am
actually thinking as Kasper seperated it is the way I'd do it now as well,
as it really makes sense to me. It's about 2 totally different usergroups !

I did a lot of projects, and I can't think of any single project where it
would have made sense to not seperate it, where it would have made sense
using the same userbase.

I remember Peter Kühn, who had some small script which adds a button in the
frontend, if for a fe-user another valid be-user exists, so he could sign in
automaticly. So, he obviously had use for it. But this is the only single
project I heard of it.

Could you please enlight me about your thoughts about the benefits of
putting them together ?

thanks,
Jan-Hendrik


BTW: Talking about LDAP once in a while... If LDAP is implemented for both,
fe as well as be users, they could just use the same tree and here we go...