Hi. I have a website where there a some different types of data (A, B, C...). The obvious solution is for me to have a separate page to display each type of data (Page_A, Page_B....). Each would have a listview to display a list of the corresponding data and each listview would be different to reflect the different types of data and also the different functionality required for each type/list. HOWEVER, there is some complex functionality separate to the actual listviews that would be common to all of the pages. This functionality is, in part, used to produce the actual datasource required for the listview.
So I have a choice. Multiple pages that have different lists displayed on each page but which replicate common functionality.
Or I create a single page that has the common functionality which also generates the datasource and that single page could have multiple listviews but then attach/bind the datasource to just one of the listviews. That would mean that there are some other listviews on the page that end up being unused. Would this cause an overhead?
Any views or comments would be really appreciated. The main functionality and code associated with the page(s) is the common code.
So I have a choice. Multiple pages that have different lists displayed on each page but which replicate common functionality.
Or I create a single page that has the common functionality which also generates the datasource and that single page could have multiple listviews but then attach/bind the datasource to just one of the listviews. That would mean that there are some other listviews on the page that end up being unused. Would this cause an overhead?
Any views or comments would be really appreciated. The main functionality and code associated with the page(s) is the common code.