sageserpent-open
commented
6 years ago Given the above, one supposes that the subscriptions should go on the world itself - as a scope fixes the revision of the parent world. One could imagine fixing the query time of the subscription - but is that a separate story? Let's keep it simple - the primary use case is to keep updated as new knowledge is made available to the world, regardless of whether it is correction to an existing event, an annulment of an existing event, a new event that advances physical time, or a back-dated new event that plugs a gap in the world's knowledge of the past.
In its most basic form, Plutonium will trigger the recalculation of a subscribed query. The query will be executed as if it had been explicitly triggered by client code; no attempt will be made to optimise the query recalculation, this story simply delivers a way of triggering without polling and only when a dependency changes as a result of a revision of the world.