It's necessary to avoid 16x html table nesting in the output page.
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
- Performance - Support fast operation with large amount of data in a nested and lookup List View (turn on server mode)
Thanks,
Dan