On 26/07/2011, at 1:04 AM, Dmitri Pal wrote:
<snip>
IMO the right thing is to decide on all this authentication,
authorization, permissions, encryption etc. in advance. Build a minimal
part and add as you go. As the component layout changes these plans
should be re-reviewed, validated and adjusted. We should get into habit
of doing it.
But at the moment I do not see a good consistent plan across the board
in the first place. Every component tries to solve the problems
differently and without joint thinking of the ultimate result. It seems
we are building patchy blanket here. I do not think customers will
appreciate it.
</rant>
"Spend time on sound planning -> Execute on the Plan" is definitely accepted
best practise. (for much more than software development too)
Regards and best wishes,
Justin Clift
--
Aeolus Community Manager
http://www.aeolusproject.org