class CAVERN_linkAttrib_c

Class for specifying the characteristics of links

Public Classes

enum CAVERN_synch_t
Choose between the types of synchronization across the links.
NONE
Perform no synchronization at all. Useful for initial synch conditions.
AUTO_SYNCH
Automatically allow CAVERNsoft to manage synchronization based on content and timestamps.
SYNCH_LOCAL_TO_REMOTE
Synchronize by tranfering data from local to remote site based on content and time stamp.
SYNCH_REMOTE_TO_LOCAL
Synchronize by tranfering data from remote to local site based on content and time stamp.
FORCE_LOCAL_TO_REMOTE
Force tranfer of data from local to remote site regardless of content and timestamp.
FORCE_REMOTE_TO_LOCAL
Force tranfer of data from remote to local site regardless of content and timestamp.
enum CAVERN_update_t
Choose between ACTIVE or PASSIVE update of linked keys.
ACTIVE
Active update means key data are synchronized whenever the data changes
PASSIVE
Passive update means the user must explicitly deliver or request data.

Public Methods

CAVERN_synch_t getInitialSynchType ()
Get initial synch type.
CAVERN_synch_t getSubsequentSynchType ()
Returns the current synch type.
CAVERN_update_t getUpdateType ()
Get update type
void setInitialSynchType (CAVERN_synch_t t)
This to set how data is initially synchronized between 2 keys when a link is first established
void setSubsequentSynchType (CAVERN_synch_t t)
This is to set how data is subsequently synchronized between 2 keys in a link
void setUpdateType (CAVERN_update_t t)
Set the link's update type to either active or passive

Public

enum CAVERN_synch_t
Choose between the types of synchronization across the links.
NONE
Perform no synchronization at all. Useful for initial synch conditions.
AUTO_SYNCH
Automatically allow CAVERNsoft to manage synchronization based on content and timestamps.
SYNCH_LOCAL_TO_REMOTE
Synchronize by tranfering data from local to remote site based on content and time stamp.
SYNCH_REMOTE_TO_LOCAL
Synchronize by tranfering data from remote to local site based on content and time stamp.
FORCE_LOCAL_TO_REMOTE
Force tranfer of data from local to remote site regardless of content and timestamp.
FORCE_REMOTE_TO_LOCAL
Force tranfer of data from remote to local site regardless of content and timestamp.
enum CAVERN_update_t
Choose between ACTIVE or PASSIVE update of linked keys.
ACTIVE
Active update means key data are synchronized whenever the data changes
PASSIVE
Passive update means the user must explicitly deliver or request data.

Documentation

Class for specifying the characteristics of links. By default links are auto-synchronizing and use active updating. That is links will compare local and remote timestamps to determine if data transfer is needed. Also when data is changed at any site, it is automatically propagated to remote sites.
ACTIVE
Active update means key data are synchronized whenever the data changes. This is similar to a server push.

void setInitialSynchType(CAVERN_synch_t t)
This to set how data is initially synchronized between 2 keys when a link is first established. When either SYNCH_LOCAL_TO_REMOTE, SYNCH_REMOTE_TO_LOCAL or AUTO are used local and remote timestamps as well as their contents are checked to decide whether data transfer is necessary.

void setSubsequentSynchType(CAVERN_synch_t t)
This is to set how data is subsequently synchronized between 2 keys in a link. In subsequent synch content nor timestamps are checked. So SYNCH_LOCAL_TO_REMOTE is the same as FORCE_LOCAL_TO_REMOTE. Similarly SYNCH_REMOTE_TO_LOCAL is the same as FORCE_REMOTE_TO_LOCAL. Note. If you use REMOTE_TO_LOCAL synching locally, any changes that you make to your local key will not be propagated to the remote subscriber/client since you have forced data transfer into being unidirectional. These rules can be overriden on temporary bases with: CAVERN_irbLink_c::requestRemote()

void setUpdateType(CAVERN_update_t t)
Set the link's update type to either active or passive. Active update means key data are synchronized whenever the data changes. In some sense this is similar to a server push. Passive update means the user must explicitly deliver or request data.


This class has no child classes.

alphabetic index hierarchy of classes


this page has been generated automatically by doc++

(c)opyright by Malte Zöckler, Roland Wunderling
contact: doc++@zib.de