AeroGearSyncClientJsonPatch 1.0.0-alpha.7

AeroGearSyncClientJsonPatch 1.0.0-alpha.7

TestsTested
LangLanguage SwiftSwift
License Apache 2
ReleasedLast Release Oct 2017
SwiftSwift Version 4.0
SPMSupports SPM

Maintained by corinne krych, Daniel Passos, Julio Cesar, Massimiliano Ziccardi.



 
Depends on:
AeroGearSyncJsonPatch= 1.0.0-alpha.7
Starscream>= 0
 

  • By
  • Red Hat, Inc.

aerogear ios sync client Build Status

This module currently build with Xcode 8 (Swift 3+) and supports iOS8, iOS9 and iOS10.

AeroGear iOS Differential Synchronization Client Engine represents a client side implementation for AeroGear Differential Synchronization (DS) Server.

This client uses the communication with the backend server implementation. The iOS SyncEngine performs the actual work of the DiffSync protocol, please refer to its README.md for more details.

Project Info
License: Apache License, Version 2.0
Build: CocoaPods
Documentation: http://aerogear.org/ios/
Issue tracker: https://issues.jboss.org/browse/AGIOS
Mailing lists: aerogear-users (subscribe)
aerogear-dev (subscribe)

Build, test and play with aerogear-ios-sync-client

  1. Clone this project

  2. Get the dependencies

The project uses cocoapods for handling its dependencies. As a pre-requisite, install cocoapods and then install the pod. On the root directory of the project run:

pod install
  1. open AeroGearSyncClientJsonPatch.xcworkspace

Adding the library to your project

To add the library in your project, you can either use CocoaPods or manual install in your project. See the respective sections below for instructions:

Documentation

For more details about the current release, please consult our documentation.

Development

If you would like to help develop AeroGear you can join our developer's mailing list, join #aerogear on Freenode, or shout at us on Twitter @aerogears.

Also takes some time and skim the contributor guide

Questions?

Join our user mailing list for any questions or help! We really hope you enjoy app development with AeroGear!

Found a bug?

If you found a bug please create a ticket for us on Jira with some steps to reproduce it.