Review of the API
Rethync API consists of two parts:
- Client part. It is used on the client (mobile devices and sometimes in desktop applications) side of the synchronization.
- Server part. It is used on the server, where the data is stored.
Client-side of the API is procedural - you execute predefined sequence of operations and called a set of methods.
Server side of the API is event-based - your code handles events initiated by the server-side engine.
Each part of the API contains an engine and one or more transports. The engine contains business logic of Rethync. Transports are used to communicate between the client and the server.
Got questions or comments about this topic? Tell us about them.