ICallbackEventHandler VS AJAX

[cherish]

They're basically the same thing... they both use the XMLHTTP object to make the request. The ICallbackEventHandler just makes things a little easier on you.

I think from the article cherish posted use the CallbackEventHandler *if* you're developing a 2.0 website and you only plan to ever run it as ASP.NET /MS.

Oh, I see. Thanks for the additional info, mmetzger.
So I guess, it basically comes down to personal preference in choosing which one to use.

EDIT:
I found another article, let me quote here a portion I think is noteworthy:

As I see it, AJAX provides two things over and beyond ICallbackEventHandler. The first feature is arbitrary parameters to the target method. The implementation uses reflection to map the incoming call onto an arbitrary method and its parameters. This is certainly convenient. The second feature going for it is generating JavaScript objects in the client script that correspond to server side types returned from the callback method. This is also very convenient.


With those two slick features over ICallbackEventHandler, it’s easy to overlook what AJAX doesn’t do well. The primary thing that ICallbackEventHandler has over AJAX is that it integrates very well into the server page lifecycle. This might seem unnecessary and it is if all your callback method is executing code unrelated to the page object on the server (like accessing a database and returning some values, say). But, integrating into the page model is essential if you want to leverage all those server controls.

Source: ICallbackEventHandler vs AJAX.NET