> How much work do you plan to do in a single request? A request is one > call to render a web page or one call to a web service. > Unless you have large tree-like structures, the performance of first > level cache can be completely neglected. If you have issues, it would > be rather beneficial to use Ayende's NHProfiler to look for > (n+1)-queries and other more impacting issues.
I'm using the nhProfiler, don't worry :) And I am fixing N+1, like, all the time. But sometimes it gets pretty complex, like when importing something from e.g. xml using webpage. > I can only maje an educated guess here: Web Forms has life cycles for > every control on the page. If you use a Scope in your > OnButtonClickedAndHurray()-code-behind-ASPX-pages, other controls may > ask for AR objects outside of that scope. SpR guards against it by > using a single scope for the whole page lifecycle. Well, the sentence in the docs/help suggested that sometimes lifecycle is run also for image requests. That's why I asked for clarification on that. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
