Server Side Initial Sync Link and Version Update Feature

[Ocean West]

I have yet to issue a 'new version' push to end users. I am curious about the following.

Currently all users followed the 4v link to download a clone and then sync.

Every time I revised the version they were prompted to download again, get a new version download and sync.

With the v5 we have the new option for server side initial sync. Haven't issued these links out yet.

Which process takes president for updates?

• clone link - all new builds are delivered as clone requiring client side initial sync
• server side link - all new builds are delivered after initial server side sync
• server side link - all new builds are delivered as clone requiring client side initial sync

Thanks

 

 

[Jesse Barnum]

Whatever type of link they originally used to download their file will be used when a version upgrade is detected. There are four combinations:

* empty clone requiring client-side sync

* empty clone with server-side initial sync

* full copy with client-side sync

* full copy with server-side sync (unless server-side filtering is being used, this particular option will probably not be faster than a client-side sync)

 

[Ocean West]

Fantastic - thanks for the clarification!