sageserpent-open
commented
6 years ago This is no longer relevant in its original form, as queries don't use patch playback - they retrieve from item state storage instead. There is a need to do incremental playback, but implementing that is tantamount to delivering #17 and #18 in one go based on the current codebase.
I'm cancelling this spike.
This is a prelude of #17 and #18.
It provides functionality to play only the patches needed to build up the correct state of a single item rendered from a scope. If several items are rendered from a scope in series (or via an applicative plus operation in the same query), then any item state shared between distinct items should not need to be recalculated. IOW, once an item has been placed into the identified item scope with the correct statte, it should be cached there.