You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SyncService is responsible for uploading Event data from an EventStore to the Paco server whenever Event data should be uploaded. It should try to run whenever there is a need to upload (experiments may decide to not upload data at all). Typically, uploading is used whenever a new event is recorded. The saving of data into the EventStore should alert the sync service. Also, relevant system events, such as network becoming available, should wake the sync service so that it can upload any data recorded while offline. The Android SyncService is a working version of a SyncService.
Issue by BobEvans
Wed Aug 28 22:46:57 2019
The SyncService is responsible for uploading Event data from an EventStore to the Paco server whenever Event data should be uploaded. It should try to run whenever there is a need to upload (experiments may decide to not upload data at all). Typically, uploading is used whenever a new event is recorded. The saving of data into the EventStore should alert the sync service. Also, relevant system events, such as network becoming available, should wake the sync service so that it can upload any data recorded while offline. The Android SyncService is a working version of a SyncService.
The Paco Server protocol for event uploading is located in the https://github.com/google/paco/blob/develop/Paco-Server/src/com/google/sampling/experiential/server/EventServlet.java
It receives an array of Events and tries to save each one to its respective Experiment's data set.
It then produces a return object which is a JSON array in order with result objects for each corresponding uploaded Event.
The text was updated successfully, but these errors were encountered: