Hi,
I'm looking at changing our project from using the old Telerik AJAX framework to the new one. The biggest problem that I can see we are going to have is with the RadAjax changes.
Currently we have one AjaxManager on the master page, but also potentially other AjaxManagers contained within various web controls. These web controls are usually CompositeControls, which need to perform asynchronous postbacks and update other controls within them.
With the old version of Telerik ajax, this has been achieved by creating an AjaxManager within the composite control and hooking up to the AjaxRequest event where the relevant code can be run. AjaxSettings can also be added to the manager to update the necessary controls. All the functionality is then encapsulated within the composite control itself.
As far as I can see, with the new framework it is recommended, or indeed required, that I have one AjaxManager per page, and all the AjaxSettings and code within my AjaxRequest event handler will have to be moved to that AjaxManager.
The problem I can see having with this is that where the old AjaxRequest on the web control would automatically only run the relevant code and update the relevant controls it will now fire all the event handlers hooked up to AjaxRequest of the master manager and update all the controls set within all the AjaxSettings.
Obviously I could perhaps make use of the event argument to only run certain bits of code when the request is fired from different places - although I'm not sure how to handle only updating certain controls - but I seem to have lost the ability to encapsulate the ajax functionality within my composite controls.
Is there an easier way? Am I missing something?
Stephen
I'm looking at changing our project from using the old Telerik AJAX framework to the new one. The biggest problem that I can see we are going to have is with the RadAjax changes.
Currently we have one AjaxManager on the master page, but also potentially other AjaxManagers contained within various web controls. These web controls are usually CompositeControls, which need to perform asynchronous postbacks and update other controls within them.
With the old version of Telerik ajax, this has been achieved by creating an AjaxManager within the composite control and hooking up to the AjaxRequest event where the relevant code can be run. AjaxSettings can also be added to the manager to update the necessary controls. All the functionality is then encapsulated within the composite control itself.
As far as I can see, with the new framework it is recommended, or indeed required, that I have one AjaxManager per page, and all the AjaxSettings and code within my AjaxRequest event handler will have to be moved to that AjaxManager.
The problem I can see having with this is that where the old AjaxRequest on the web control would automatically only run the relevant code and update the relevant controls it will now fire all the event handlers hooked up to AjaxRequest of the master manager and update all the controls set within all the AjaxSettings.
Obviously I could perhaps make use of the event argument to only run certain bits of code when the request is fired from different places - although I'm not sure how to handle only updating certain controls - but I seem to have lost the ability to encapsulate the ajax functionality within my composite controls.
Is there an easier way? Am I missing something?
Stephen