differences in running through pagelifecycle

[Martin Gleiß]

Hi,

actually I'm looking for a method for loading data in a control with  most minimal action on the server. (Means, when possible, only the control that needs to be refreshed should go through its lifecycle, not the rest of the pages controls).

I found some Information that it should be possible to handle this problem with RadXMLHttpPanel, but no exact information how to ensure that only the refreshed control goes through its lifecycle.

Any hints ?

As additional Information: We have a page that is build by WebParts encapsulating usercontrols. Our need ist to force single webparts/usercontrols to refresh by button/timer etc.

[Pero]

Hello Martin,

The RadXmlHttpPanel uses either ASP.NET client callbacks or Web Services to update its content. This means that the lifecycle of the page is wholly dependent on this technologies.
The Web Service is a lighter than the ASP.NET client callback, because only the object passed to the set_value method is sent to the server. In the case with the callback, the values of all FORM fields, such as hidden fields (including the view state field) are sent to the server.
This being said I believe the Web Service approach will be the one to take. Here is a tutorial from our online documentation, that shows how to configure the XmlHttpPanel to work with web service: http://www.telerik.com/help/aspnet-ajax/radxmlhttppanel-webservice-configuration.html.

Regards,
Pero
the Telerik team