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: Connecting to a new site

Berkeley DB Reference Guide:
Berkeley DB Replication

 PrevRefNext

Connecting to a new site

Connecting to a new site in the replication group happens whenever the DB_ENV->rep_process_message function returns DB_REP_NEWSITE. The application should assign the new site a local environment ID number, and all future messages from the site passed to DB_ENV->rep_process_message should include that environment ID number. It is possible, of course, for the application to be aware of a new site before the return of DB_ENV->rep_process_message (for example, applications using connection-oriented protocols are likely to detect new sites immediately, while applications using broadcast protocols may not).

Regardless, in applications supporting the dynamic addition of database environments to replication groups, environments joining an existing replication group may need to provide contact information. (For example, in an application using TCP/IP sockets, a DNS name or IP address might be a reasonable value to provide.) This can be done using the cdata parameter to the DB_ENV->rep_start function. The information referenced by cdata is wrapped in the initial contact message sent by the new environment, and is provided to the existing members of the group using the rec parameter returned by DB_ENV->rep_process_message. If no additional information was provided for Berkeley DB to forward to the existing members of the group, the data field of the rec parameter passed to the DB_ENV->rep_process_message function will be NULL after DB_ENV->rep_process_message returns DB_REP_NEWSITE.

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 @d2 1 a2 1 a3 1 d18 1 a18 1 DB_ENV->rep_process_message method returns DB_REP_NEWSITE. The application d31 1 a31 1 the cdata parameter to the DB_ENV->rep_start method. The information d37 1 a37 1 parameter passed to the DB_ENV->rep_process_message method will be NULL after @ 1.1.1.3 log @Import: RPM 4.1 @ text @d2 1 a2 1 d4 1 d19 1 a19 1 DB_ENV->rep_process_message function returns DB_REP_NEWSITE. The application d32 1 a32 1 the cdata parameter to the DB_ENV->rep_start function. The information d38 1 a38 1 parameter passed to the DB_ENV->rep_process_message function will be NULL after @ 1.1.1.4 log @Import: RPM 4.1.1 @ text @d2 1 a2 1 a3 1 d18 1 a18 1 DB_ENV->rep_process_message method returns DB_REP_NEWSITE. The application d31 1 a31 1 the cdata parameter to the DB_ENV->rep_start method. The information d37 1 a37 1 parameter passed to the DB_ENV->rep_process_message method will be NULL after @