Why RadarCube ASP.NET RIA?
Posted by - NA - on 19 November 2008 06:48 PM
While the whole world is constantly moving towards the web-based applications we are not standing still. And we are glad and proud to offer the new major release of our ASP.NET controls: RadarCube ASP.NET RIA controls. These are web-based ASP.NET OLAP controls built in accordance with the RIA technology (Whats RIA).
So let’s take a look why the new components can be marked as a new era in ASP.NET OLAP development, and what is distinguishing them from the other tools available on the market.
1. This is the only OLAP Client, built to meet the RIA standards, and giving a user an overwhelming level of interactivity within web-pages: context-depending menus, dragging, smoothing, transparency, animated elements, selection ranges (both table cells and graph elements) and much more. Rich Internet Applications are much more responsive than traditional web applications that must always interact with a remote server.
2. New charting ASP.NET OLAP control named RIA OLAP Chart developed to bring the Visual Analysis technology to RadarCube ASP.NET users. While ASP.NET OLAP Grid allows working with numbers, RIA OLAP Chart allows representing your data graphically. This gives users a unique opportunity to analyze their business data visually, dealing with charts rather than numbers, which is much easier to perceive. Now it's easier than ever to spot new trends and discover unknown problems in your data flow. No matter what industry you're working in: banking, sales, insurance, marketing, or manufacturing. RIA OLAP Chart will help you gain an insight into your data and make new discoveries right from your web browser.
3. Client/Server balance. A Rich Web Control comprises of two parts: server (ASP.NET control) and client (Silverlight-application). The ASP.NET code provides interaction with data providers, and also prepares the data for the client. The client part provides data visualization and interaction with the end user. The two parts are connected using AJAX technology. This approach frees server resources, allowing more client sessions to work concurrently.
4. The new OLAP controls are fully PROTECTED. The client receives only visualization data in a form of an XML-string. Any information concerning data sources or the like does NOT get to the client (in contrast to stand-alone silverlight applications).
5. Client Visualization of tables and images takes virtually no traffic! The XML-code passed to the client side is much more saving than HTML-fragments passed by common OLAP clients. This is of vital importance for Visual OLAP – instead of the static images the client takes XML-data so that the end Silverlight-application can build the full-blown dynamic graphs. The traffic size (and therefore the response time) at that is getting tens and hundreds times less.
6. More operation on the client side. The client silverlight-application allows to perform many important operations on the client side, without wasting time for additional server requests. For example, such operations like graph type changing, zooming, series color and point size changing, applying visual filters to the rendered data, and much more, all this is done completely on the client side, all in dynamic mode in no time at all.
7. Ease of developing. The silverlight-application that visualizes the OLAP data is provided by the ASP.NET control, and doesn’t require the developer to have a slightest idea of Silverlight, WPF, or XAML technology. All the developer needs is put the Grid or Chart on the ASP.NET page and tune the data source.
8. Ease of migration. The beauty of the new ASP.NET RIA controls is that current users can migrate to the RIA version without any hard changes in the existing code. You can get to know how to move to the new release from here.
9. HTML OLAP Grid twin. The RIA OLAP Grid component comes along with its HTML twin, so in case you can’t use the RIA version of the OLAP Grid (due to some special company security rules, for example) you can still use its HTML version.
10. Minimal developer requirements. The developer only needs Visual Studio 2005 or Visual Studio Developer Edition and .NET Framework 3.5 SP1 installed.