Field Level Merge
GoZync3.FieldLevelMerge History
Hide minor edits - Show changes to output
Changed line 21 from:
Field-level merge has its own overhead, so while it can really speed things up, it only does so in some cases. Read more on this here: [[speed]].
to:
Field-level merge has its own overhead, so while it can really speed things up, it only does so in some cases and is less useful (and slower) on the Pull than on the Push. Read more on this here: [[speed]].
Changed line 21 from:
Field-level merge has it's own overhead though, so while it can really speed things up, it only does so in some cases. Read more on this here: [[speed]].
to:
Field-level merge has its own overhead, so while it can really speed things up, it only does so in some cases. Read more on this here: [[speed]].
December 18, 2012, at 10:12 AM
by - minor edits and clarifications
Changed lines 5-6 from:
Then come back here and learn what field-level merge is all about and when it can make your syncs faster.
to:
Then come back here and learn what field-level merge is all about, and when it can make your syncs faster.
Changed lines 11-16 from:
When this is turned on, GoZync will only send the fields that have been changed since the last zync, instead of sending the whole record.
This can be a huge help if both the mobile user and hosted usersmay be editing the same record: if you edit someone's phone number, and I edit their name, field-level merge lets both those edits get to the same record.
Or imagine that you have a collection of photos about a buildingthe iPad. Without field-level merge, editing the caption of one photo would cause all the photos on that record to be sent up to the server: with field-level we only send the caption.
This can be a huge help if both the mobile user and hosted users
Or imagine that you have a collection of photos about a building
to:
When this is turned on, GoZync will only send the fields that have been changed since the last Zync, instead of sending the whole record.
This can be a huge help if both the mobile user and hosted users are editing the same record. If you edit someone's phone number, and I edit their name, field-level merge lets both those edits get to the same record.
Or imagine that you have a collection of photos about a building on your iPad. Without field-level merge, editing the caption of one photo would cause all the photos on that record to be sent up to the server: with field-level we only send the caption.
This can be a huge help if both the mobile user and hosted users are editing the same record. If you edit someone's phone number, and I edit their name, field-level merge lets both those edits get to the same record.
Or imagine that you have a collection of photos about a building on your iPad. Without field-level merge, editing the caption of one photo would cause all the photos on that record to be sent up to the server: with field-level we only send the caption.
Changed lines 19-20 from:
We have some notes on this under the heading [["speed"]], but field-level merge can also make your zyncs much faster, as there is less data being sent. This is especially true with photos, if you're only editing some of the photos some of the time.
to:
We have some notes on this under the heading [["speed"]], but field-level merge can also make your Zyncs much faster, as there is less data being sent. This is especially true with photos, if you're only editing some of the photos some of the time.
Added lines 1-6:
!! For your first zync, turn field-level merge off.
Field-level merge can make first syncs slower than normal, so while you're testing, have it off unless you have a lot of container fields.
Then come back here and learn what field-level merge is all about and when it can make your syncs faster.
Field-level merge can make first syncs slower than normal, so while you're testing, have it off unless you have a lot of container fields.
Then come back here and learn what field-level merge is all about and when it can make your syncs faster.
Changed lines 3-4 from:
to:
This is an optional setting on the Zync Options tab of GoZyncHosted (select a layout on the Dashboard, then click "Integration & Options" and you'll see a tab for Zync Options).
When this is turned on, GoZync will only send the fields that have been changed since the last zync, instead of sending the whole record.
This can be a huge help if both the mobile user and hosted users may be editing the same record: if you edit someone's phone number, and I edit their name, field-level merge lets both those edits get to the same record.
Or imagine that you have a collection of photos about a building the iPad. Without field-level merge, editing the caption of one photo would cause all the photos on that record to be sent up to the server: with field-level we only send the caption.
When this is turned on, GoZync will only send the fields that have been changed since the last zync, instead of sending the whole record.
This can be a huge help if both the mobile user and hosted users may be editing the same record: if you edit someone's phone number, and I edit their name, field-level merge lets both those edits get to the same record.
Or imagine that you have a collection of photos about a building the iPad. Without field-level merge, editing the caption of one photo would cause all the photos on that record to be sent up to the server: with field-level we only send the caption.
Changed lines 13-15 from:
We have some notes on this under the heading [["speed"]] but field-level merge can also make your zyncs much faster, as there is less data being sent. This is especially true with photos, if you're only editing some of the photos some of the time.
to:
We have some notes on this under the heading [["speed"]], but field-level merge can also make your zyncs much faster, as there is less data being sent. This is especially true with photos, if you're only editing some of the photos some of the time.
Field-level merge has it's own overhead though, so while it can really speed things up, it only does so in some cases. Read more on this here: [[speed]].
Field-level merge has it's own overhead though, so while it can really speed things up, it only does so in some cases. Read more on this here: [[speed]].
Changed line 7 from:
We have some notes on this under the heading [["speed"]] but field-level merge can also make your zyncs much faster as there is less data being sent. This is especially true with photos, if you're only editing some of the photos some of the time.
to:
We have some notes on this under the heading [["speed"]] but field-level merge can also make your zyncs much faster, as there is less data being sent. This is especially true with photos, if you're only editing some of the photos some of the time.
Added lines 6-7:
We have some notes on this under the heading [["speed"]] but field-level merge can also make your zyncs much faster as there is less data being sent. This is especially true with photos, if you're only editing some of the photos some of the time.
Changed lines 1-2 from:
!! What is field level merge?
to:
!! What is field-level merge?
Changed lines 3-5 from:
Coming soon.
to:
Coming soon.
%center% %width=500px newwin% [[http://www.seedcode.com/screenshots/gozync/flmoptions.png | http://www.seedcode.com/screenshots/gozync/flmoptions.png]]
%center% %width=500px newwin% [[http://www.seedcode.com/screenshots/gozync/flmoptions.png | http://www.seedcode.com/screenshots/gozync/flmoptions.png]]
