We have a new web application that we are working to design and then develop. Our original intention was to run everything through components - the data access, business logic as well as the HTML pages themselves. I know that usually one wouldn't do the HTML pages in components themselves, but our thought was to create templates that could be called to create pages dynamically. Essentially, we could create a single ASP page and then the remaining data to be fed into the page would be contained in the URL. We were planning on having a data storage table in our database that would keep each of the pages and related information/code that would be associated with each. This way, if we needed to make changes, we could simply make changes to the database data instead of having to re-code the components, re-compile and then wait for a week for our server group to load the new component.
However, our concern is whether we are making this too complicated. We thought maybe we're just better off doing all of the data access and business logic in components and then just doing the ASP pages normally and it might equate the same in the end. Anyone have any thoughts on this would be greatly appreciated. Thanks. Insanity is merely a state of mind while crazy people have a mind of their own.
However, our concern is whether we are making this too complicated. We thought maybe we're just better off doing all of the data access and business logic in components and then just doing the ASP pages normally and it might equate the same in the end. Anyone have any thoughts on this would be greatly appreciated. Thanks. Insanity is merely a state of mind while crazy people have a mind of their own.