Customize The Sync
GoMaps.CustomizeTheSync History
Hide minor edits - Show changes to output
Deleted lines 8-9:
Changed line 13 from:
GoZync makes it very easy to do this by syncing a found set of data from your hosted file. And you can build that found set using straightforward find scripts you already know how to write. More here: [[GoZync3.Downloading Found Sets | Downloading Found Sets]].
to:
GoZync makes it very easy to do this by syncing a found set of data from your hosted file. And you can build that found set using straightforward find scripts you already know how to write. More here: [[GoZync5.Downloading Found Sets | Downloading Found Sets]].
Changed lines 5-6 from:
GoMaps uses GoZync to sync, so you have the same options here as in any GoZync deployment: useful to review those here: [[GoZync3.ZyncOptions | Zync Options]].
to:
GoMaps uses GoZync to sync, so you have the same options here as in any GoZync deployment: useful to review those here: [[GoZync5.ZyncOptions | Zync Options]].
Changed lines 9-10 from:
(In a "round trip", users push then process the sync into your hosted file during the sync--using the iOS processor--which can be slow. A "push" drops off the sync payload and then disconnects, leaving the processing for a [[GoZync3.AutoProcessing | server-side script]] to take care of.)
to:
(In a "round trip", users push then process the sync into your hosted file during the sync--using the iOS processor--which can be slow. A "push" drops off the sync payload and then disconnects, leaving the processing for a [[GoZync5.AutoProcessing | server-side script]] to take care of.)
Changed line 17 from:
And of course, checking out the GoZync docs in their entirety can help: [[GoZync3.GoZync3 | GoZync Documentation]].
to:
And of course, checking out the GoZync docs in their entirety can help: [[GoZync5.GoZync5 | GoZync Documentation]].
Changed lines 9-10 from:
(In a "round trip", users push then process the sync into your hosted file during the sync--using the iOS processor--which can be slow. A "push" drops off the sync payload and then disconnects, leaving the processing for a [[GoZync3.AutoProcessing | server-side script]] to take care of.
to:
(In a "round trip", users push then process the sync into your hosted file during the sync--using the iOS processor--which can be slow. A "push" drops off the sync payload and then disconnects, leaving the processing for a [[GoZync3.AutoProcessing | server-side script]] to take care of.)
Changed lines 15-17 from:
GoZync makes it very easy to do this by syncing a found set of data from your hosted file. And you can build that found set using straightforward find scripts you already know how to write. More here: [[GoZync3.Downloading Found Sets]].
links to GZ docs
links to GZ docs
to:
GoZync makes it very easy to do this by syncing a found set of data from your hosted file. And you can build that found set using straightforward find scripts you already know how to write. More here: [[GoZync3.Downloading Found Sets | Downloading Found Sets]].
And of course, checking out the GoZync docs in their entirety can help: [[GoZync3.GoZync3 | GoZync Documentation]].
And of course, checking out the GoZync docs in their entirety can help: [[GoZync3.GoZync3 | GoZync Documentation]].
Changed lines 13-14 from:
to:
Whenever you have a big data set (big in terms of the number or records OR in terms of photos) it's important to limit the sync to just the data your user needs. That's often just "their" records, or "their records that need to be inspected today".
GoZync makes it very easy to do this by syncing a found set of data from your hosted file. And you can build that found set using straightforward find scripts you already know how to write. More here: [[GoZync3.Downloading Found Sets]].
GoZync makes it very easy to do this by syncing a found set of data from your hosted file. And you can build that found set using straightforward find scripts you already know how to write. More here: [[GoZync3.Downloading Found Sets]].
Changed lines 3-4 from:
Overview
to:
'''Overview'''
Changed lines 7-10 from:
round trips
to:
The big difference between most Zync deployments and GoMaps is that Maps has a lot of photos coming down to the mobile device, and often has photos going back up. So while most folks just run a "round trip" sync, you may want to run separate push and pull syncs so your mobile users aren't processing the whole sync during their "push"
(In a "round trip", users push then process the sync into your hosted file during the sync--using the iOS processor--which can be slow. A "push" drops off the sync payload and then disconnects, leaving the processing for a [[GoZync3.AutoProcessing | server-side script]] to take care of.
'''Found Sets: Pulling down just "my" properties'''
adfasd
(In a "round trip", users push then process the sync into your hosted file during the sync--using the iOS processor--which can be slow. A "push" drops off the sync payload and then disconnects, leaving the processing for a [[GoZync3.AutoProcessing | server-side script]] to take care of.
'''Found Sets: Pulling down just "my" properties'''
adfasd
Changed lines 3-4 from:
to:
Overview
GoMaps uses GoZync to sync, so you have the same options here as in any GoZync deployment: useful to review those here: [[GoZync3.ZyncOptions | Zync Options]].
GoMaps uses GoZync to sync, so you have the same options here as in any GoZync deployment: useful to review those here: [[GoZync3.ZyncOptions | Zync Options]].
Added lines 1-9:
!! Creating your own sync workflow
concepts
found sets
round trips
links to GZ docs
concepts
found sets
round trips
links to GZ docs
