Skip Headers

Oracle TopLink Developer's Guide 10g Release 3 (10.1.3) B13593-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# Database Sessions

A database session provides a client application with a single data source connection, for simple, standalone applications in which a single connection services all data source requests for one user.

Figure 75-8 TopLink Database Session Architecture

A database session is the simplest session TopLink offers. It provides both client and server communications and supports only a single client and a single database connection. It is suitable for simple applications or 2-tier applications.

Note: Oracle does not recommend using this session type in a 3-tier application because it is not as flexible or scalable as a server and client session. Oracle recommends that you use server sessions and client sessions (see "Server and Client Sessions"). Applications that are built using database sessions may be difficult to migrate to a scalable architecture in the future.

A database session contains and manages the following information:

- An instance of `Project` and `DatabaseLogin`, which store database login and configuration information

- The JDBC connection and the database access

- The descriptors for each of the application persistent classes

- Identity maps that maintain object identity and act as a cache

For more information, see the following:

- "Creating Database Sessions"

- "Configuring Database Sessions"

- "Acquiring a Session from the Session Manager"