Saturday, October 6, 2007

ComponentOne WebDataObjects for ASP.NET

ComponentOne WebDataObjects for ASP.NET extends the power of ComponentOne DataObjects for .NET for your Web applications. Especially important in WebDataObjects is its server-side caching. Since HTTP is a stateless protocol, it is typically necessary to cache data on the server to achieve satisfactory performance. Although facilitated to a certain degree by ASP.NET, this task is perhaps the most challenging when building Web database applications, and one that requires extensive manual coding. Even more importantly, the need to cache data on the server in absence of proper tools often forces developers to abandon rich data models such as data sets in favor of primitive data sources such as forward-only data readers. The inability to effectively use data sets on the server leads to dramatic increase in development time for Web Forms applications in comparison to Windows Forms. With ComponentOne WebDataObjects and its server side caching, session caching, memory resident tables, and automatic object pooling, building powerful database web applications is now a breeze.

Latest News about ComponentOne WebDataObjects for ASP.NET

Individual Sales of this component are no longer available - you must purchase as part of suite - posted 5/21/2007

Starting 5/21/07, renewal skus for individual products and individual studios are no longer offered except under special circumstances. This is the final phase of ComponentOne's year-long transition from single components to exclusively offering the ComponentOne Studio Enterprise suite of developer tools. For more information, ComponentOne Studio Enterprise


Image Gallery - Click Image to Enlarge
ComponentOne WebDataObjects for ASP.NET ComponentOne WebDataObjects for ASP.NET ComponentOne WebDataObjects for ASP.NET ComponentOne WebDataObjects for ASP.NET
ComponentOne WebDataObjects for ASP.NET




Detailed Product Description

ComponentOne WebDataObjects Features:


  • Use the same code in Windows Forms and Web Forms
  • Server side caching provides scalability
  • Server side caching: Make your ADO.NET datasets reside on the server
  • Central repository to avoid data modification conflicts.
  • Immediate access to large datasets
  • Automatic object pooling support

  • No comments: