Can someone help me map out in my brain why Kendo is better than ASPNET AJAX controls?
It is my understanding that using Kendo, is really the same as including a bunch of jquery libraries in your web page and then using them on the page. And how do they ensure you have purchased a license and havent simply downloaded the source and included it in your site?
So, doesn't that introduce the same problem I am currently dealing with on an MVC web site I took over from another developer?
On that site, they have over 2 MB of css and js files included on every web page.
Only a small fraction of the code will ever be used.
I realize there are some things I can do to make that situation better- move the .js links to the bottom of the page, minimize the files, remove unused ones etc... but it still seems inifficient to me.
When using server controls, if my understanding is correct- doesnt a server control automatically push out ONLY the javascript required for the control to work resulting in a much smaller footprint?
It is my understanding that using Kendo, is really the same as including a bunch of jquery libraries in your web page and then using them on the page. And how do they ensure you have purchased a license and havent simply downloaded the source and included it in your site?
So, doesn't that introduce the same problem I am currently dealing with on an MVC web site I took over from another developer?
On that site, they have over 2 MB of css and js files included on every web page.
Only a small fraction of the code will ever be used.
I realize there are some things I can do to make that situation better- move the .js links to the bottom of the page, minimize the files, remove unused ones etc... but it still seems inifficient to me.
When using server controls, if my understanding is correct- doesnt a server control automatically push out ONLY the javascript required for the control to work resulting in a much smaller footprint?
1 Answer, 1 is accepted
0
Hi Bill,
I cannot say that KendoUI is better than the RadControls for ASP.NET AJAX. They are two completely different sets of tools that are built around completely different paradigms. Depending on the scenario and the developer preferences, either of them can offer a lot of benefits over the other.
The KendoUI scripts can be fragmented so only necessary pieces are included depending on what you intend to use on the given page, if this helps in your case.
With the server IScriptControls - indeed, each control only registers the scripts it needs (you can find a detailed list here: http://www.telerik.com/help/aspnet-ajax/introduction-disabling-embedded-resources.html). What is important here is that there is a set of scripts that you cannot avoid:
- the MS AJAX framework itself. RadControls for ASP.NET AJAX are built on top of it
- the webforms scripts (that may be considered part of the MS AJAX framework)
- some of our core scripts (Core.js, jQuery are the ones all controls will need)
These scripts are served through webresource requests and here are some tips on optimizing them:
- until the app pool is recycled webresource requets are cached. Longer restart intervals allow for better caching.
- you can use RadScriptManager - it can combine scripts into a single request: http://www.telerik.com/help/aspnet-ajax/scriptmanager.html.
- you can use a CDN to download the scripts as separate files from an external server. This can improve their caching (it depends on the client browser cache and not on your servers recycling): http://www.telerik.com/help/aspnet-ajax/scriptmanager-cdn-support.html.
Please note, however, that we do not recommend and support the integration of the RadControls for ASP.NET AJAX in MVC environments, because they are not designed for this. I have already explained that in your other thread but I wanted to make sure it is available here as well.
Regards,
Marin Bratanov
Telerik
I cannot say that KendoUI is better than the RadControls for ASP.NET AJAX. They are two completely different sets of tools that are built around completely different paradigms. Depending on the scenario and the developer preferences, either of them can offer a lot of benefits over the other.
The KendoUI scripts can be fragmented so only necessary pieces are included depending on what you intend to use on the given page, if this helps in your case.
With the server IScriptControls - indeed, each control only registers the scripts it needs (you can find a detailed list here: http://www.telerik.com/help/aspnet-ajax/introduction-disabling-embedded-resources.html). What is important here is that there is a set of scripts that you cannot avoid:
- the MS AJAX framework itself. RadControls for ASP.NET AJAX are built on top of it
- the webforms scripts (that may be considered part of the MS AJAX framework)
- some of our core scripts (Core.js, jQuery are the ones all controls will need)
These scripts are served through webresource requests and here are some tips on optimizing them:
- until the app pool is recycled webresource requets are cached. Longer restart intervals allow for better caching.
- you can use RadScriptManager - it can combine scripts into a single request: http://www.telerik.com/help/aspnet-ajax/scriptmanager.html.
- you can use a CDN to download the scripts as separate files from an external server. This can improve their caching (it depends on the client browser cache and not on your servers recycling): http://www.telerik.com/help/aspnet-ajax/scriptmanager-cdn-support.html.
Please note, however, that we do not recommend and support the integration of the RadControls for ASP.NET AJAX in MVC environments, because they are not designed for this. I have already explained that in your other thread but I wanted to make sure it is available here as well.
Regards,
Marin Bratanov
Telerik
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed now.