August 25, 2005

Using the Domain Objects Persistence Pattern in .NET

hen developing object-oriented applications that use relational databases, creating a domain object design that’s consistent with the database design makes applications easier to understand, because domain objects typically represent real-life “entities” and their relationships with each other. Therefore, in many situations, the domain objects are “mapped” to the relational database

ICEfaces Offers a Novel, Pure Java Approach to the Rich vs. Thin Dilemma

hen it comes to their GUIs, distributed applications have always observed a pendulum effect. The early enterprise distributed application comprised a heavy centralized server with a dumb terminal for data entry. As the personal computer evolved, the model changed; increased power at the desktop led to heavier and more sophisticated