To answer this question, we take a look at a simple example and we will contrast a non data-bound and a data-bound solution to display a set of data.
The inspiration for this example is associated with our experience in developing the C3D travel blog sample application. While being away in China, we were entering our travel experiences in the travel blog. We split up our long trip into parts, to get a better overview and to have more than one trip to show you, with realistic content. Therefore, we now have a list of trips, although still from only one user.
Assume that we would like to show an overview of the trips on our C3D website. We could display a simple HTML table, and it would look like this:
Even if you use fancy MVC techniques to develop your server-side application and templates to produce the view output, the final HTML source that is sent to the client browser has the data content mixed with the HTML table structure tags, as in the following code...