Web Grid, Client side Binding VS. Server side HTML generation

Posted by Ron Harlev on Stack Overflow See other posts from Stack Overflow or by Ron Harlev
Published on 2009-07-14T19:24:31Z Indexed on 2010/05/08 18:48 UTC
Read the original article Hit count: 277

Filed under:
|
|
|

I'm working on replacing an existing web grid in an ASP.NET web application, with a new implementation. The existing grid is powerful, but not flexible enough. It also brings with it all kind of frameworks we don't like to have on our web pages.

While looking into existing options I noticed I can break the available solutions into two main approaches. The older approach is represented best by the ASP.NET GridView. This is a classic ASP.NET control that generates the needed HTML on the server, based on a given set of data. The newer approach is depending on client side rendering, mainly with jQuery. A good example would be jqGrid. Only the data is sent to the client (Usually with JSON or XML)

In the GridView case, if I want an AJAX behavior, I would have to implement it with something like an update panel.

  • Is there a definitive choice I should make?
  • Is there a good chance of achieving the same snappy behavior I get with jqGrid (even with many records), with server side rendered controls?
  • Is there some hybrid implementation incorporating both approaches?

© Stack Overflow or respective owner

Related posts about ASP.NET

Related posts about jQuery