The Files
GoZync3.TheFiles History
Hide minor edits - Show changes to output
December 10, 2012, at 03:43 AM
by - editing and clarifying
Changed lines 9-12 from:
This is the file containing your Inbox, where records from your mobile file(s) are sent before being processed into records in your solution: GoZyncHosted is the intermediary file. This file is completely unlocked.
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution just to push recordsup. They just need access rights in GoZyncHosted. It is also a very light file and using anything heavier can slow down the connections required to zync with your mobile file.
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution just to push records
to:
This is the file containing your Inbox, where records from your mobile file(s) are sent before being processed into records in your solution. GoZyncHosted is the intermediary file. This file is completely unlocked.
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution just to push records to the server. They just need access rights in GoZyncHosted. It is also a very light file. Using anything heavier can slow down the connections required to Zync with your mobile file.
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution just to push records to the server. They just need access rights in GoZyncHosted. It is also a very light file. Using anything heavier can slow down the connections required to Zync with your mobile file.
Changed lines 17-18 from:
This file is largely locked and manages your license (the number of mobile devices allowed to connect). You can, however, modify the layouts if you want to change the way it looks. (Your mobile users will probably never see this file of course.)
to:
This file is largely locked and manages your license (the number of mobile devices allowed to connect). You can, however, modify the layouts if you want to change the way it looks. (Your mobile users will probably never see this file, of course.)
Changed line 27 from:
A thin version of GoZyncHosted for on your mobile device, GoZyncMobile is also unlocked and contains all the mobile-side scripting logic for performing a zync. GZM also contains a list of apps you're syncing and the last sync log, so it can act as a launching pad for your zynced mobile apps.
to:
A thin version of GoZyncHosted for on your mobile device, GoZyncMobile is also unlocked and contains all the mobile-side scripting logic for performing a Zync. GoZyncMobile also contains the list of apps you're syncing and the last sync log, so it can act as a launching pad for your Zynced mobile apps.
Changed lines 7-17 from:
!! GoZyncConnector
This is the file containing your Inbox, where records from your mobile file(s) are sent before being processed into records in your solution. GoZyncConnector is the intermediary file. This file is completely unlocked.
(If you really need to, you can add the scripts, layouts, and graph from this file into your own file and dispense with GoZyncConnector itself. If you know how to do this kind of thing, have at it. If not, %newwin% [[http://www.seedcode.com/cp-app/contact/1 | get in touch]] and we can get you a quote for doing that for you.)
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution. They just need access rights in GoZyncConnector. It is also a very light file and using anything heavier can slow down the connections required to zync with your mobile file: so we recommend keeping Connector as a separate file.
!! GoZync
This
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into
!! GoZync
to:
!! GoZyncHosted (GZH)
This is the file containing your Inbox, where records from your mobile file(s) are sent before being processed into records in your solution: GoZyncHosted is the intermediary file. This file is completely unlocked.
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution just to push records up. They just need access rights in GoZyncHosted. It is also a very light file and using anything heavier can slow down the connections required to zync with your mobile file.
GoZyncHosted also contains the interface used to check your work when integrating GoZync into your own file. It holds your integration settings and [[Zync Options]] for each table you're zyncing.
!! GoZyncLicense
This is the file containing your Inbox, where records from your mobile file(s) are sent before being processed into records in your solution: GoZyncHosted is the intermediary file. This file is completely unlocked.
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution just to push records up. They just need access rights in GoZyncHosted. It is also a very light file and using anything heavier can slow down the connections required to zync with your mobile file.
GoZyncHosted also contains the interface used to check your work when integrating GoZync into your own file. It holds your integration settings and [[Zync Options]] for each table you're zyncing.
!! GoZyncLicense
Changed lines 21-27 from:
!! Mobile (Your mobile file)
> > notes
!! _GoZyncUtility
This file is placed on your iPad when you first connect to the host from your mobile file. _GoZyncUtility helps manage our connection to your host / server and is locked. Your users will never interact with it directly and if they happen to delete it from their iPhone or iPad, GoZync will replace it for you.
!! _GoZyncUtility
This
to:
!! QuickContact (Your mobile file)
QuickContact is our example file: the file standing in for the mobile file your users will be interacting with on their iPad, iPhone, or laptop. Learn more about QuickContact [[SampleFiles | here]].
!! GoZyncMobile (GZM)
A thin version of GoZyncHosted for on your mobile device, GoZyncMobile is also unlocked and contains all the mobile-side scripting logic for performing a zync. GZM also contains a list of apps you're syncing and the last sync log, so it can act as a launching pad for your zynced mobile apps.
QuickContact is our example file: the file standing in for the mobile file your users will be interacting with on their iPad, iPhone, or laptop. Learn more about QuickContact [[SampleFiles | here]].
!! GoZyncMobile (GZM)
A thin version of GoZyncHosted for on your mobile device, GoZyncMobile is also unlocked and contains all the mobile-side scripting logic for performing a zync. GZM also contains a list of apps you're syncing and the last sync log, so it can act as a launching pad for your zynced mobile apps.
Changed lines 13-15 from:
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution. They just need access rights in GoZyncConnector.
to:
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution. They just need access rights in GoZyncConnector. It is also a very light file and using anything heavier can slow down the connections required to zync with your mobile file: so we recommend keeping Connector as a separate file.
Changed lines 11-12 from:
to:
(If you really need to, you can add the scripts, layouts, and graph from this file into your own file and dispense with GoZyncConnector itself. If you know how to do this kind of thing, have at it. If not, %newwin% [[http://www.seedcode.com/cp-app/contact/1 | get in touch]] and we can get you a quote for doing that for you.)
Changed lines 13-15 from:
One nice thing about having this in a separate file is that you mobile users don't need to authenticate into your real solution. They just need access rights in GoZyncConnector.
to:
One nice thing about having this in a separate file is that you mobile users don't need to [[security | authenticate]] into your real solution. They just need access rights in GoZyncConnector.
Changed line 26 from:
This file is placed on your iPad when you first connect to the host from your mobile file. _GoZyncUtility helps manage our connection to your host / server and is locked. Your users should never see it
to:
This file is placed on your iPad when you first connect to the host from your mobile file. _GoZyncUtility helps manage our connection to your host / server and is locked. Your users will never interact with it directly and if they happen to delete it from their iPhone or iPad, GoZync will replace it for you.
Added lines 3-4:
! On the Host or Server
Added lines 17-26:
! On the Mobile Device
!! Mobile (Your mobile file)
> > notes
!! _GoZyncUtility
This file is placed on your iPad when you first connect to the host from your mobile file. _GoZyncUtility helps manage our connection to your host / server and is locked. Your users should never see it
Changed lines 1-3 from:
Note that we have a nice little
to:
''Note that we have a nice little %newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/GoZyncMap.png | map]] of this that may help.''
!! GoZyncConnector
This is the file containing your Inbox, where records from your mobile file(s) are sent before being processed into records in your solution. GoZyncConnector is the intermediary file. This file is completely unlocked.
Now you can add the scripts, layouts, and graph from this file into your own file and dispense with GoZyncConnector itself. If you know how to do this kind of thing, have at it. If not, %newwin% [[http://www.seedcode.com/cp-app/contact/1 | get in touch]] and we can get you a quote for doing that for you.
One nice thing about having this in a separate file is that you mobile users don't need to authenticate into your real solution. They just need access rights in GoZyncConnector.
!! GoZync
This file is largely locked and manages your license (the number of mobile devices allowed to connect). You can, however, modify the layouts if you want to change the way it looks. (Your mobile users will probably never see this file of course.)
!! GoZyncConnector
This is the file containing your Inbox, where records from your mobile file(s) are sent before being processed into records in your solution. GoZyncConnector is the intermediary file. This file is completely unlocked.
Now you can add the scripts, layouts, and graph from this file into your own file and dispense with GoZyncConnector itself. If you know how to do this kind of thing, have at it. If not, %newwin% [[http://www.seedcode.com/cp-app/contact/1 | get in touch]] and we can get you a quote for doing that for you.
One nice thing about having this in a separate file is that you mobile users don't need to authenticate into your real solution. They just need access rights in GoZyncConnector.
!! GoZync
This file is largely locked and manages your license (the number of mobile devices allowed to connect). You can, however, modify the layouts if you want to change the way it looks. (Your mobile users will probably never see this file of course.)
Added lines 1-3:
!! Which files does GoZync require?
Note that we have a nice little map of this that may help
Note that we have a nice little map of this that may help
