Building a precise Frame Cache is a tough job, and is doomed to fail when attempting to tie cache invalidation to state changes. The only viable path is to create a system of systematic tagging of processing steps, and use this as foundation for chained hash values, linked in accordance to the actual processing structure. This is complicated by the secondary concern of maintaining memory efficacy for the render node model, which can be expected to grow to massive scale. And even while this invocation can not be fully devised right now, an attempt can be made to build a foundation that is not outright wasteful, by detaching the logical information from the specific weaving pattern used for implementation, and by minimising the representation in memory and computing the compound information on-demand.... |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| dump | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||