Hallo, Ian Bicking hat gesagt: // Ian Bicking wrote: > Well, here's how I'd imagine it going: > > * Your class raises AuthorizationRequired
I'd just like to point out, that in a lot of applications Pages do not *require* login, but provide it as a service. For example slashdot.org doesn't have "AuthorizationRequired" but offers advanced customization to registered and logged-in users. Most of the times in these kinds of apps, the "LoginPage" isn't a real Page, but a LoginBox as a part of the Page. This seems to not fit well with exceptions, because the LoginBox is not the result of an exception occuring in the Page, it's normal behaviour. But this is just a feeling, probably exceptions can be made to handle the AuthorizationPossible case as well. ciao -- Frank Barknecht _ ______footils.org__ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
