>>Hi,
>>
>>I am wondering at one aspect of an ASP.NET application - drop-down list of some sort. For example, say a form has a pull-down list control of Customers. In ASP.NET Web Forms app I would fill a dataset/datatable form the DB table and bind the drop-down control to the datatable. So the entire list of, e.g. Customers, is converted into HTML values. Therefore, my understanding is that the speed of the page depends on how large the HTML page is (depending on number of records in the dataset).
>>
>>How is it different in the MVC design? In terms of speed? The data still has to be bound to a drop-down list, right? How is it done, in a very general explanation?
>>TIA.
>
>There's no "binding" per say. There's a helper that actually builds the HTML dropdown elements based specified items. Generally you shape your data into a pre-definited structure and provide that to the helper.
I think I see. But, as Craig said, since the data has to be "translated" into an HTML, the speed difference between the two technologies won't be that great (if any). Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
