Uploaded image for project: 'GPII - Global Public Inclusive Infrastructure'
  1. GPII - Global Public Inclusive Infrastructure
  2. GPII-434

Upgrade all settings handlers and lifecycle actions to be asynchronous

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Needs more info
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None

      Description

      An architectural limitation since the first implementation of the architecture is that all actions issued by the Flow Manager must complete synchronously. This has generally not been an issue on Linux since all of its settings are performed by gsettings, which appears to complete synchronously, or the rewriting of files.

      This has become a more urgent issue on Windows since although calls made to the SpiSettingsHandler appear to complete synchronously, the OS in practice takes a significant time to honour them, and it appears that if a further SPI call is made during this time window, the state of the system will become corrupted.

      A simple scheme for now would be for either

      i) a settings handler to be able to unilaterally return a promise (detectable by the core architecture), or
      ii) for it to issue metadata in its grade indicating that it accepts a callback.

      This work is blocking GPII-581 which in turn blocks GPII-94

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              amb26 Antranig Basman
              Reporter:
              kasper Kasper Markus
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: