Uploaded image for project: 'Nuxeo Drive '
  1. Nuxeo Drive
  2. NXDRIVE-2091

Wait for the server configuration before starting features

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0
    • Fix Version/s: 4.4.2
    • Component/s: Configuration
    • Release Notes Summary:
      Waiting for the server before starting features
    • Release Notes Description:
      Hide

      As the server configuration endpoint can be used to enabled/disable features and tweak parameters impacting all users, it was the natural move to first wait for it before starting features.

      Here is the flow when starting the application:
      1. Launch engines (an engine is an account).
      2. Fetch the server configuration endpoint.
      3. Update options, merge with one from the local configuration file.
      4. Start (or deny) all features.

      Show
      As the server configuration endpoint can be used to enabled/disable features and tweak parameters impacting all users, it was the natural move to first wait for it before starting features. Here is the flow when starting the application: 1. Launch engines (an engine is an account). 2. Fetch the server configuration endpoint. 3. Update options, merge with one from the local configuration file. 4. Start (or deny) all features.
    • Tags:
    • Sprint:
      nxDrive 11.1.30
    • Story Points:
      2

      Description

      As the server config is used to enabled/disable features and tweak parameters impacting all users, then Drive should first wait for it before trying to start them.

      For instance, only the synchronization status can be toggled, but more are coming and this ticket will be usefull (cf NXDRIVE-2070).

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 3 hours
                1d 3h