Compression for ASP.NET AJAX

Overview

RadCompression is a proud member of Telerik’s AJAX family of performance optimization helper controls. It automatically ZIP-s the AJAX and WebService responses for even faster data transfers and improved page performance. The compression process is completely transparent to your client-side code (JavaScript or Silverlight) and your server-side code.

See Demos Download Trial

Features

• Types of Compressed Content
• ViewState Compression
• AJAX Responses Performance Tests
• ViewState Compression Performance Tests

• Types of Compressed Content

  Telerik ASP.NET AJAX Compression is not designed to be a complete replacement for other HTTP compression tools, such as the built-in HTTP Compression in IIS 7. Instead, it is designed to work with those existing tools to cover scenarios they usually miss - namely the compression of bits moving back and forth in AJAX (and now Silverlight) applications. Telerik ASP.NET AJAX Compression will automatically detect and compress requests that expect these content response types (as found in the HTTP request's "ContentType" header or "AcceptsTypes" header):
  

  • application/x-www-form-urlencoded
  • application/json
  • application/xml
  • application/atom+xml
    
    These types generally reflect the content types returned by AJAX Web Services, ADO.NET Data Services, and AJAX UpdatePanel responses, though there certainly are other scenarios that return these content types .

  Top

• ViewState Compression

  Telerik ASP.NET Compression can also automatically compress ViewState. Enabling ViewState compression with the RadCompression module does not require changes to your code, or changes to your markup, and not even a change to your web.config. The only thing you need to do is add a new Browser file to your web project (or modify your Browser file if you’re already using one).

  Top

• AJAX Responses Performance Tests

  Scenarios:
  1. UpdatePanel Updates: In this scenario, there is a page with a RadGrid, bound server-side during the NeedsDataSource RadGrid event, with a RadAjaxManager on the page to "ajaxify" all Grid operations.
  2. Client-binding Updates: In this scenario, there is a page with a RadGrid that is declaratively bound to a ADO.NET Data Service (which, for the unfamiliar, is essentially a fancy WCF web service). The RadGrid fetches data via the service and initializes in the browser and uses the web service for all operations, such as paging.For both scenarios, the data layer is a simple LinqToSql model using the AdventureWorks database. Both grids are bound to all Employees in the AdventureWorks data store. For each scenario, we'll test the following, measuring bytes sent during the request, bytes sent in the response, total requests, and page load time:
  
  Results
  
  Average Bytes Received
  
  With UpdatePanels and "traditional" AJAX, bytes sent over the wire are reduced by about 68% with RadCompression enabled, and by about 86% with client-side binding.
  
  Read the article for full details

  Top

• ViewState Compression Performance Tests

  Scenario:
  A simple page with a RadGrid that loads data from the AdventureWorks Employees table. RadGrid is declaratively bound to an EntityDataSource, starting from 10 records to 240 per page.
  
  Results
  
  
  

  The blue bars represent the ViewState size (in KB) with RadCompression. The green bars represent the difference in the original ViewState size (i.e. total size with no compression). And the red numbers indicate the compression “efficiency” at each step. On average, Telerik ASP.NET Compression reduced ViewState size by 61%! (omitting the “0” tests)

  Read the article for full details

  Top