RE: Exception Handling Opinion 2004-12-14 - By J. Ambrose Little
Philip,
This (the return code) approach is what I have implemented for my
generic authentication provider. I agree it is the most elegant
solution for this particular problem.
BTW, I'm more than happy to share the authentication provider code
with anyone. It's not polished, but it seems to work. :) Just ping
me offlist.
--Ambrose
On Tue, 14 Dec 2004 06:14:07 -0800 (PST), Philip Nelson
<panmanphil@(protected)> wrote:
> > to determine which login has failed. The reason being one of the sites has
> > it's own error page content. So, the user should receive a general login
> > failed message but customized to the login type.
>
> So, wouldn't that be a "failed login page" then? As opposed to an error page.
>
> About the only thing really not covered here has been the return code approach
> that at times can be very useful. I use just that for login. I have an enum of
> login results, success, loginfailure, lockout. No exceptions needed at all. At
> any time if you can accomodate the caller with a return value that helps the
> caller determine what to do with good or bad requests, you have made a more
> robust system.
>
> I like to think about a customer (caller) coming up to a bank teller (object)
> and asking for a service (message). The teller may be able to do the service
> (success case) may have more questions (handled error) or may have redirect
the
> user somewhere else (exception).
>
> =====
> Philip - http://blogs.xcskiwinn.org/panmanphil
> "There's a difference between righteous anger and just being crabby" - Barbara
Need SQL Advice? http://sqladvice.com
Need RegEx Advice? http://regexadvice.com
Need XML Advice? http://xmladvice.com
|
|
