Clever Geek Handbook

What are the benefits of XML Data Model in DataSet Model?

In my current job, we have a .NET / SQL Server based CMS. While setting up multiple modules for some internal use, I was a bit surprised to see that instead of having APIs that returned data via your typical result set bound to a DataGrid / DataList / Repeater control, the APIs returned XML node / collection which is then passed to the XSLT transformation and displayed on the page that way.

What are the advantages of using such a model?

+1


source to share


4 answers


Using XSLT transformations will allow you to use a different layout and formatting than standard .Net web controls. Some people discourage the use of .Net grids because they can include more HTML than necessary and because if they are not handled carefully, they can bloat the ViewState.



Recent discussion here is about .Net networks being bloatware (but developers use them anyway).

0


source


The displayed pages can be of any type, for example html, php, etc.



0


source


By setting up the datasource and xml that the page just transforms, you also instantly create a simple "web service" that can be used by other software. For example, it would be trivial to turn this grid into an RSS feed, or write a program to periodically flush this data and send more urgent alerts.

0


source


XSLT method is very MVC, unit testing, standalone solution friendly, where ASP.NET has good control over ... no.

Caveat: I reject the suggestion that MS can write better html / css / js than I can. ASP.NET controls are awkward abominations.

0


source






More articles:


All Articles