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.