head 1.2; access; symbols RPM_4_2_1:1.1.1.4 RPM_4_2:1.1.1.4 RPM_4_1_1:1.1.1.4 RPM_4_1:1.1.1.3 RPM_4_0_5:1.1.1.2 RPM_4_0_4:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.55.29; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2002.01.08.00.30.12; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2002.01.08.00.30.12; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2003.01.18.13.49.03; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2002.01.17.20.11.42; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2003.01.18.14.05.00; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB Reference Guide: Replication environment IDs

Berkeley DB Reference Guide:
Berkeley DB Replication

 PrevRefNext

Replication environment IDs

Each database environment included in a replication group must have a unique identifier for itself and for the other members of the replication group. The identifiers do not need to be global, that is, each database environment can assign local identifiers to members of the replication group as it encounters them. For example, given three sites: A, B and C, site A might assign the identifiers 1 and 2 to sites B and C respectively, while site B might assign the identifiers 301 and 302 to sites A and C respectively. Note, it is not wrong to have global identifiers, of course, it is just not necessary.

It is the responsibility of the application to label each incoming replication message passed to DB_ENV->rep_process_message function with the appropriate identifier. Subsequently, Berkeley DB will label outgoing messages to the send interface with those same identifiers.

Negative identifiers are reserved for use by Berkeley DB, and should never be assigned to environments by the application. Two of these reserved identifiers are intended for application use, as follows:

DB_EID_BROADCAST
The DB_EID_BROADCAST identifier indicates a message should be broadcast to all members of a replication group.

DB_EID_INVALID
The DB_EID_INVALID identifier is an invalid environment ID, and may be used to initialize environment ID variables that are subsequently checked for validity.

PrevRefNext

Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Import: RPM 4.0.4 @ text @@ 1.1.1.2 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d24 2 a25 2 302 to sites A and C respectively. Note that it is not wrong to have global identifiers, it is just not a requirement. d27 1 a27 1 replication message passed to DB_ENV->rep_process_message method with the appropriate @ 1.1.1.3 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d25 2 a26 2 302 to sites A and C respectively. Note, it is not wrong to have global identifiers, of course, it is just not necessary. d28 1 a28 1 replication message passed to DB_ENV->rep_process_message function with the appropriate @ 1.1.1.4 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d24 2 a25 2 302 to sites A and C respectively. Note that it is not wrong to have global identifiers, it is just not a requirement. d27 1 a27 1 replication message passed to DB_ENV->rep_process_message method with the appropriate @