|
@@ -205,14 +205,15 @@ Chapter 1. User's Guide
|
|
|
recovers, the module makes sure that no stale contacts are returned
|
|
|
from it.
|
|
|
|
|
|
- Write queries are replicated to two databases, depending on some
|
|
|
- distribution keys, e.g. the username and domain of some subscribers.
|
|
|
- Its main field of application is for storing and retrieving location
|
|
|
- data. The actual database for this subscriber is choosen from a set
|
|
|
- that is specified in the master database. Read queries are executed on
|
|
|
- one database of the set. If this database is not available, the other
|
|
|
- database would be used. This failure is recorded in the master
|
|
|
- database.
|
|
|
+ Write queries are replicated to two or more databases, depending on
|
|
|
+ some distribution keys, e.g. the username and domain the subscribers.
|
|
|
+ The number of databases used for replication is configurable at compile
|
|
|
+ time by modifying the DB_NUM define. Its main field of application is
|
|
|
+ for storing and retrieving location data. The actual database for this
|
|
|
+ subscriber is choosen from a set that is specified in the master
|
|
|
+ database. Read queries are executed on one database of the set. If this
|
|
|
+ database is not available, the other database would be used. This
|
|
|
+ failure is recorded in the master database.
|
|
|
|
|
|
Connections to the distributed databases are setup prior the actual
|
|
|
query is executed. The module maintains a cache of the database handles
|