Hi to all .NET gurus,
we evaluated the new Application Block "Authorization and Profiler
Application Block" for using with role based authorization.
Our results:
- No roles in roles can be managed (that is a must in a role based
system)
- In every check there is no caching between them (performance sucks)
- Dynamic object creation in every access (performance sucks)
- Profiles and Principals must be handled completely seperated (??)
- In every access check you have to build up parameters etc - this
handling is
unbelievable overhead!!
- You have to cast the principal for every access (you better use a
gerneric
class with static helpers here!)
So the result is: Use it to play a bit and use it for very small
example applications. It is a good example for newbies out there - and
the pluggable system in this block was a good idea (not new but fine)!
I work for companies like BASF, DaimlerChrysler, BMW etc. and i have
implemented some role based access systems before in .NET - but this
block doesn't fit for them.
I can't understand why they did not optimize it - other blocks have
caching etc. in it?
You can implement own providers etc. but thats somewhat dumb that you
better build up your own system with caching, expirations etc...
Let me know if there are questions - i develop open source software
and im .NET consultant for different companies out there.
Greetings and happy programming
Ralf
|
Similar Threads
