The ReplicationConfig type exposes the following members.
 Fields
Fields
| Name | Description | |
|---|---|---|
|  | AutoInit | 
            If true, the replication master will automatically re-initialize
            outdated clients (defaults to true). 
             | 
|  | BulkTransfer | 
            If true, the replication master will send groups of records to the
            clients in a single network transfer
             | 
|  | DelayClientSync | 
            If true, the client will delay synchronizing to a newly declared
            master (defaults to false). Clients configured in this way will
            remain unsynchronized until the application calls
            RepSync()()(). 
             | 
|  | Elections | 
            If true, Replication Manager automatically runs elections to
            choose a new master when the old master appears to
            have become disconnected (defaults to true).
             | 
|  | InMemory | 
            If true, replication only stores the internal information in-memory
            and cannot keep persistent state across a site crash or reboot. By
            default, it is false and replication creates files in the
            environment home directory to preserve the internal information. 
            This configuration flag can only be set before the
            DatabaseEnvironment is opened.
             | 
|  | NoBlocking | 
            If true, Berkeley DB method calls that would normally block while
            clients are in recovery will return errors immediately (defaults to
            false).
             | 
|  | RepMgrAckPolicy | 
            Specify how master and client sites will handle acknowledgment of
            replication messages which are necessary for "permanent" records.
            The current implementation requires all sites in a replication group
            configure the same acknowledgement policy. 
             | 
|  | RepmgrSitesConfig | 
            A list of site configurations.
             | 
|  | Strict2Site | 
            If true, the Replication Manager will observe the strict "majority"
            rule in managing elections, even in a group with only 2 sites. This
            means the client in a 2-site group will be unable to take over as
            master if the original master fails or becomes disconnected. (See
            the Elections section in the Berkeley DB Reference Guide for more
            information.) Both sites in the replication group should have the
            same value for this parameter.
             | 
|  | Transport | 
            The delegate used to transmit data using the replication
            application's communication infrastructure.
             | 
|  | UseMasterLeases | 
            If true, master leases will be used for this site (defaults to
            false). 
             | 





