Hi,
I got a situation with nested Ajax Managers (I use Manager Proxy in nested one). Main Manager sets ajax request to RadGrid, and in this grid in edit form I got drop down with AutoPostBack, on which other drop down is updated - it works perfect, but it updates whole Grid.
So I decided to add AjaxManagerProxy in this form and set it for this DropDown, but when I check in FireBug it looks like whole Grid is updated anyway. It's way to much data to be send and receive for only one DropDown.
Is there some nice solution to minify bandwidth in such a case?
Gr,
Pawel
I got a situation with nested Ajax Managers (I use Manager Proxy in nested one). Main Manager sets ajax request to RadGrid, and in this grid in edit form I got drop down with AutoPostBack, on which other drop down is updated - it works perfect, but it updates whole Grid.
So I decided to add AjaxManagerProxy in this form and set it for this DropDown, but when I check in FireBug it looks like whole Grid is updated anyway. It's way to much data to be send and receive for only one DropDown.
Is there some nice solution to minify bandwidth in such a case?
Gr,
Pawel
1 Answer, 1 is accepted
0
sitefinitysteve
Top achievements
Rank 2
Iron
Iron
Veteran
Rank 2
Iron
Iron
Veteran
answered on 20 Oct 2009, 02:26 AM
You can try yanking the viewstate out...Todd put up a video on RadGrid optimization http://tv.telerik.com/aspnet/radgrid/optimizing-radgrid-aspnet-ajax
Also there's the RadCompression Module which is supposed to help compress Ajax requests
If there's just too much data going back and forth, maybe you should look into the ClientSide API on the RadControls and just hook the RadCombos up to a webservice