We will probable have a Sync Manager, FHSyncConfig, AGSyncConfig etc. SyncManager may be able to wrap the adapters in classes to give native Android sync. Regardless we will need a few drafts to figure this out.
- Figure out a way to do auth
- Feed Henry has an Authentication Mechanism. We will probably need to figure out how to hook AG stuff into it.
- Seems like the FH android libs auth isn't fully baked in yet.
- Make a cookbook app for sync based on shoot and share
- Ideas include an ascii art shoot and share because ag-ss only supports text
- FH does polling for its sync. Will probably need to make sure we can turn it on and off without subscribing/unsubscribing (IE if networking is bad or if the user is near a data cap or wants to conserve battery).
-
Authentication
-
May need to expand the auth or authz package to be aware of Authentication Manager
-
See http://developer.android.com/training/sync-adapters/creating-sync-adapter.html
-
NOTE Android native sync needs implementations for Content Provider, Authenticator, Authenticator Service, Sync Adapter, and Sync Adapter Service to work. These are going to be Helper Classess.
-
Using the XMPP stuff will make things a lot easier on the client side. Android handles all of the complicated state transitions, retries, etc.
-
Feed Henry
-
Create helper classes
-
Create Tutorials
-
AeroGear Sync Server
-
Create helper classes
-
Create Tutorials