Uploaded image for project: 'Fluid Infusion'
  1. Fluid Infusion
  2. FLUID-6543

Allow model bindings to be established prior to bound components existing

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Nexus
    • Labels:
      None

      Description

      One of the Nexus' design goals is that it should be configurable entirely through static, declarative document-like data such as Kettle configs and co-occurrence engine recipes. Therefore all the Nexus mechanisms for modifying and binding to component trees should work independently of the order in which the client or server end comes online, and should be tolerant to either end temporarily going offline.

      For model bindings, this means that it should be possible for a client to open a bindModel WebSocket connection to a non-existent component, delaying the "initModel" message until the component is created.

      This is a continuation of FLUID-6504, which expanded the model binding API with typed messages and error reporting.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ptcher Philip Tchernavskij
              Reporter:
              ptcher Philip Tchernavskij
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated: