Chapter 6. Gateways
In Chapter 5, we explored and developed Data Access Objects (DAOs) for our application that managed single-record transactions one row of data inserted, updated, deleted, or returned at any one time and how the Bean object was used as the blueprint to hold and manage the values returned from the DAO queries.
Having dealt with these single-record transactions, we now need to focus on reading and handling results from a database query or data provider that returns multiple records per transaction.
Managing an application that may hold and use large amounts of content from a data provider can be a daunting task at times.
It is not uncommon for applications to feature large search interfaces, perhaps with pagination, such as lists of users within a contact application, for example.
When developing object-oriented applications, the burden of dealing with large queries such as these can be easily managed by wrapping all relevant code into one object, a Gateway.
In this chapter...
