You're right about catch being expensive. It appears to use an additional 40 - 60 ms. the good news is that it is not a percentage so the added time on long running pages is sometimes on the lower end.
If there is any other way I would use it, but the code that throws the FlexWikiAuthorizationException has no understanding of the context it was called in, which is the correct design. Without such a fix dynamically created topic content fails to work if a single topic has restricted read for a user. This would make the wiki useless. John Davidson On 9/28/07, Nathan Jones <[EMAIL PROTECTED]> wrote: > > > I worry a little about performance. The catch can get expensive. I'm not > where I can really go on about it, but it is something to think about > > ------------------------------------------------------------------------- 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
