ASP.NET Ajax with GridView

<Edit> This thread has been split off of this thread</edit>


In theory, it should work relatively well... the downside is that if you've got a grid that you want to autopostback every single cell, then you've got unnecessary overhead of all the UpdatePanel instances... and if you use only a single UpdatePanel to wrap the whole grid, it doesn't fix the need to click twice on the cell you wish to select...

That won't work in the case of the OP who needs it to refresh data on the page - however, if it's just one textbox, then having the UpdatePanel around the list that needs updating and pointing the trigger to the textbox should work nicely.

I see your point...

In the GridView case I wouldn't consider using UpdatePanels for all of my cells...because, like you've said there would be a lot of overhead. I would look into writing my own Ajax to handle this. Even though UpdatePanels are convenient to quickly add Ajax capabilities to web apps., they are not always the best way to solve the problem.

Aside from that, you have to post back to the server regardless of whether it's to update a single element or the majority of the web page.

Even though asynchronous calls update a portion of the web page when the request returns, the ASP cycle remains the same... So the same amount of sever-side processing will need to be done regardless of whether you only want to update a single element or the whole web page.

Correct me if I'm wrong here, but I'm pretty sure it's the same overhead for full page updates as it is for partial page updates.

For the GridView...have you considered creating a custom object that implements both the ITemplate Interface and IScriptControl Interface....where your scripts make Ajax calls to the server to update that row?

You're entirely correct. The UpdatePanel posts the whole page via an asynchronous javascript call, and the entire page life cycle is processed. The page is then rendered and sent back to the client where the javascript's callback pulls the html/script that is contained within the <ContentTemplate> tags of the received XML and replaces the data displayed on screen with it.

So as far as the server is concerned, if the postback occurs from an UpdatePanel or is an entire page postback, it's the same. It's just that the javascript handles it differently on the client side.

If you write your own javascript that contains an AJAX call however, you could have it call to a webmethod that just processes received data which could be as much or as little as needs to be posted to the server. It processes that data and passes back just the data that the AJAX call requests at which point, the javascript callback can do whatever you want. In this case, find the object in the document and replace its value, rather than replacing a whole block of html.

This way is much more efficient in terms of network and processing, but is a lot more intensive for the programmer...

Of course, wrapping every object with an UpdatePanel adds to the amount of processing the server needs to do in every case. It still needs to convert the XHTML to HTML and handle the viewstate etc etc etc...

We should move these posts to another thread instead of hijacking this one...

I was thinking the exact same thing.
Do you have an existing thread on this topic?

Not yet, but I may do when I get as far as trying to fix this bug. I have more pressing issues to solve (and by pressing I mean interesting :))

I've been trying a whole bunch of new (new for me at least) web technologies/techniques lately and this thread came to mind.

Apparently calling web services using JavaScript is a lot easier now :) You can create web methods that return JSON Objects and this simplifies things quite a bit in the JavaScript side of things. To get your web methods to return JSON Objects All you have to do is indicate that you want to use the Script.Services.ScriptService()

I've been starting to get away from the ASP.NET controls (like GridViews) lately and have found that it's making for a much lighter web application.

If you have time I'd recommend exploring this. Also, you should check out ASP.NET MVC (because it's absolutely awesome too!)