Summary
Developing an application using a three-tier architecture design requires some additional upfront design and coding time, but this time is well worth it in the long run because of the advantages you gain from separating the UI code from the business and data handling logic. In this article, I've demonstrated one design I've found effective for accomplishing this. In the next article in this series, I'll enhance the Web UI to allow new Publishers to be added and existing ones to be deleted, and will show you how you can protect your data from errors that might be caused by multiuser concurrency problems.