FLUID-4790: Super Applier should support all features of a normal applier.

Metadata

Source
FLUID-4790
Type
Task
Priority
Major
Status
Closed
Resolution
Duplicate
Assignee
y z
Reporter
y z
Created
2012-09-06T10:08:56.172-0400
Updated
2013-08-22T15:56:36.578-0400
Versions
  1. 1.4
Fixed Versions
N/A
Component
  1. Data Binder
  2. Framework

Description

Currently super applier supports fireChangeRequest.
We also need to support modelChanged listeners and guards.

Comments

  • Antranig Basman commented 2013-08-22T15:56:36.568-0400

    In the years since we constructed the first vestigial "superapplier", our thinking about how to deal with relationships amongst the tree of models, and in general, FLUID-3674 has changed - the original idea of composing a tree of cooperating appliers and models has emerged as just a special case of the requirements of what we now think of as the "model relay" system, now mostly described by FLUID-5024 and FLUID-5045. In this new model, models and appliers are essentially "isolated" and connected only by streams of ChangeApplier events, and we intend to cut down on cases where model objects are genuinely shared amongst multiple components (in the style of CSpace).

    This issue is being closed in favour of the ModelRelay issues which cover all the use cases of this JIRA and several more - and in fact we should construct a separate JIRA for the removal of the existing SuperApplier implementation which will become redundant once ModelRelay is complete.