Uploaded image for project: 'Realm Core'
  1. Realm Core
  2. RCORE-1082

SyncSocketProvider eventloop migration

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      Once the DefaultSocketProvider has been created, this task is to migrate everything to use the Service event loop in the DefaultSocketProvider and move the Service thread from SyncClient into that class.

      Things to consider - the flx_harness uses Client directly and calls run() on its own thread as well as stopping the Sync Client. This will need to be reworked, since the event loop will be working differently. Also, the Sync Client startup/teardown process must be able to run cleanly without stopping the event loop thread.

      In addition, the binding_callback_thread_observer will need to be called directly from the DefaultSocketProvider thread when it starts, an error occurs or the thread exits. We will also need some sort of error callback to pass exceptions that occur in the thread up to the Sync Client.

            Assignee:
            michael.wilkersonbarker@mongodb.com Michael Wilkerson-Barker (Inactive)
            Reporter:
            pavel.yakimenko@mongodb.com Pavel Yakimenko (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: