Alternatives for Managing Connections
Both explicit and implicit connections have a place in your application design strategies, depending on how the connections are used. Here are some strategies for connection management that you should consider:
*Use implicit connections for early prototyping. You would then add explicit connections to the design as it matures, or as problems surface.
*Instantiate a set number of RWDBConnections per RWDBDatabase. You would use the same connections for all operations for which a connection can be specified. This strategy is useful for environments that have an actual ceiling on the number of connections your application can access.
*Use the connection pool of the DB Interface Module to optimize your application. By allocating a pool adequate to your needs at program start up, and reusing those connections, considerable performance advantages may be realized. You may have to experiment in order to determine exactly what size is right for you.
For many applications, explicit connections have some advantages over implicit connections, including:
*total control over managing your connections, which can lead to enhanced performance. After you read the sections on inserters, see A Note About Connections.
*full transaction control. See Transaction Processing with RWDBConnection, which follows.