Currently, controllers are created each time a user visits a view.
Since the best practice is to specify the TargetXXX properties of the controller (see also the Q182831 issue), we could accept this statement as a strict rule and then do not create a corresponding controller only if it is already exists for a view with the same configuration.
This will allow us to significantly increase performance, especially taking into account a huge number of controllers in a real world application.
Thanks,
Dennis
Ticket
S30935
Visible to All Users
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
See also:
- Performance.Web - Share common parts of the application model to reduce startup time and memory use
- Performance.Web - Support the Web Garden mode
- Performance - Public results of benchmark tests of XAF Win and Web applications
- Documentation - Describe product requirements (Win and Web) for development and deployment environments
- Web.Performance - Reduce traffic between web server and client browsers
- Layout.Web.Performance - Simplify the structure of ASP.NET Property Editors and controls to improve client-side performance
- Layout.Web.Performance - Simplify the Web layout, a complex nested structure of tags yields poor performance
- Performance - Optimize the mechanism of creating controllers
Thanks,
Dan
Hello,
This feature was implemented in version v2010 vol 2 for Windows Forms applications only (See Also: Layout.Win - Low performance when opening a Detail View containing a lot of tabs). Further details on this can be found at
XAF – Detail View Performance Improvements (Coming in V2010 Vol 2).
Please track the Web - Support lazy View items initialization in ASP.NET applications suggestion to be automatically notified when it is implemented for XAF ASP.NET applications.
Thanks,
Dennis