Asynchronous question - Ajax or .NET 2.0?

I finally get some time to start writing some code with .NET 2.0. One thing I was starting recently to use was to implement asynchronous programming AJAX.

Really nice work, but a lot of code client and server side included. Just wondering if it doesn't worth to do the same using the new asynchronous features of  ASP.NET 2.0?

Otherwise, what are the main differences between AJAX and .NET 2.0, anf if I choose the first, can my web application be compatible with the latter?

 

1 Comment

  • If you are talking about client callbacks in ASP.NET 2.0 you are talking about something like AJAX. Requests will be invoked from the client-side JavaScript using XmlHttpRequests, IFRAMES,... to refresh parts of the HTML page using DHTML/DOM.



    Because AJAX is not a standard, it is something that will use different technologies.



    If I look at my Ajax.NET library, this is something different to the client callbacks used in ASP.NET 2.0. My first idea was to create a way to get objects back to the client rather than to update controls.



    I think the best is to use ASP.NET 2.0 callbacks where it is enough to get simple strings. If you want to build more complex requests you can use libraries like Ajax.NET.



    The Live WebControls from dart.com are already using AJAX methods to update sever controls like ASP.NET 2.0 is doing.

Comments have been disabled for this content.