Cascade download Cascade download is a mechanism in which the referring syncbo downloads the referred syncbo’s to any depth during synchronization from device. Cascade download of a referring syncbo would succeed only if all the referred syncbo’s can be downloaded .otherwise, it fails. Cascade download flag can only be set for relationship between syncbos. Let’s consider four syncbo’s in design time.
Let’s create the instances of these syncbo’s. The syncbo’s are Timed two way (T01) type.
Case 1: mobile device synchronizing syncbo A for the first time and all instances of syncbos are present as follows in Replica database.
After synchronizing Syncbo A, these instances will be present on the device. Bo c – cTop Bo d – dTop, d010 Bo b – bTop, b010 Bo a – aTop, a010, a020 Case 2: mobile device synchronizing syncbo A for the first time and bTop of Syncbo b is absent.
After synchronizing Syncbo A, these instance will be present on the device. Nothing will get downloaded Case 3: mobile device synchronizing syncbo A for the first time and cTop of syncbo c is not present 
After synchronization of Syncbo A , these instance will be present on the device. Nothing will get downloaded. Case 4: mobile device synchronizing syncbo A for the first time and dTop of syncbo d is not present.
After synchronization of syncbo A , these instance will be present on the device. Bo c – cTop Bo b – bTop, b010 Bo a – aTop, a010 Case 5: mobile device synchronizing syncbo A for the first time and b010 of syncbo b is not present
After synchronization these instance will be present on the device. Bo c – cTop Bo d – dTop, d010 Bo b – bTop Bo a – aTop, a010, a020 Case 6: mobile device synchronizing syncbo A for the first time and a010 of syncbo a is not present.
After synchronizing Syncbo A, these instance will be present on the device. Bo c – cTop Bo d – dTop, d010 Bo b – bTop, b010 Bo a – aTop, a020 Case 7: mobile device synchronizing syncbo A for the first time and a020 of syncbo a is not present.
After synchronization Syncbo A, these instance will be present on the device. Bo c – cTop Bo b – bTop, b010 Bo a – aTop, a010 ************ END ********************** Note: The filter by reference with cascade download would be dealt in detail in the later blogs. Till then stay tuned.
Let’s create the instances of these syncbo’s. The syncbo’s are Timed two way (T01) type. Case 1: mobile device synchronizing syncbo A for the first time and all instances of syncbos are present as follows in Replica database. After synchronizing Syncbo A, these instances will be present on the device. Bo c – cTop Bo d – dTop, d010 Bo b – bTop, b010 Bo a – aTop, a010, a020 Case 2: mobile device synchronizing syncbo A for the first time and bTop of Syncbo b is absent. After synchronizing Syncbo A, these instance will be present on the device. Nothing will get downloaded Case 3: mobile device synchronizing syncbo A for the first time and cTop of syncbo c is not present After synchronization of Syncbo A , these instance will be present on the device. Nothing will get downloaded. Case 4: mobile device synchronizing syncbo A for the first time and dTop of syncbo d is not present. After synchronization of syncbo A , these instance will be present on the device. Bo c – cTop Bo b – bTop, b010 Bo a – aTop, a010 Case 5: mobile device synchronizing syncbo A for the first time and b010 of syncbo b is not present After synchronization these instance will be present on the device. Bo c – cTop Bo d – dTop, d010 Bo b – bTop Bo a – aTop, a010, a020 Case 6: mobile device synchronizing syncbo A for the first time and a010 of syncbo a is not present. After synchronizing Syncbo A, these instance will be present on the device. Bo c – cTop Bo d – dTop, d010 Bo b – bTop, b010 Bo a – aTop, a020 Case 7: mobile device synchronizing syncbo A for the first time and a020 of syncbo a is not present. After synchronization Syncbo A, these instance will be present on the device. Bo c – cTop Bo b – bTop, b010 Bo a – aTop, a010 ************ END ********************** Note: The filter by reference with cascade download would be dealt in detail in the later blogs. Till then stay tuned.
5 Comments
