> An exception is roughly 1000x as slow as "normal" flow control statements. > So the general rule of thumb is that if the exception is likely to occur > more than one in a thousand times you perform an operation, you might want > to consider a normal return code instead of an exception. Witness > Int32.Parse and Int32.TryParse. Or TextReaderForTopic versus HasPermission. > :) >
It seems to me that authorization is most certainly not something that would fall into this category. It kind of goes against the "Exceptions should be exceptional" rule (I may have made that one up, but you can get the drift.) :) I'm not sure that authorization failures in a system that is aware of authorization should really even get treated as exceptions in the first place.... I'm not suggesting that that get changed, but I do think that the treatment by "user" code (ie wikitalk) should be as if authorization is something tested for, not exceptional.... Anyway, I think that I've said all that I can on the subject. I don't wanna get too soapboxy. :) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
