Changes between Version 2 and Version 3 of Session2

Timestamp:

Oct 1, 2015, 12:21:42 AM (10 years ago)

Author:

Greg Couch

Comment:

--

Session2

@@ -11 +11 @@
 == The Problem ==
 
-Ideally, when restoring a session, all data that is referenced by some other data has already been restored.  So the all of dependencies need to be known by the saving code and there can be no circular dependencies.  This avoids two-phase initialization, which is especially important for C++ objects.
+Ideally, when restoring a session, all data that is referenced by some other data has already been restored.  Therefore all of dependencies need to be known by the saving code and there can be no circular dependencies.  This avoids two-phase initialization, which is especially important for C++ objects.
 
 === Where is Session State? ===
@@ -42 +42 @@
 
 * How to give dependencies for ordering session data?
+  * naive data with back references are circular
+  * may need to give before and after dependencies
 * What is the granularity?
 * Can we guarantee non-circular references?
+* Can we provide a "simple" API for tools?
+
+== Part of the Solution ==
+
+Saving protocol:
+1. visit all session state and record:
+  * what tool is responsible for the state
+  * what data it refers to and
+    * only referred to data needs to be named
+1. save the list of used tools
+1. serialize state
+  * keep track of named data that was saved
+1. confirm that all referred to data was saved
+
+Restoring protocol:
+1. Read the list of used tools
+  * if installed tools are insufficient, then give user option to cancel or load tools
+1. deserialze state inside block/unblock of triggers
+