Changes between Version 7 and Version 8 of Session2

Timestamp:

Oct 12, 2015, 11:49:13 AM (10 years ago)

Author:

Greg Couch

Comment:

--

Session2

@@ -22 +22 @@
 
 == Protocols ==
+
+For discussion purposes, any method we choose for session files will need to follow the following protocols (the solution will have more details):
 
 === Saving protocol: ===
@@ -117 +119 @@
 On the Python side, it is possible to provide an API that takes simple data and implements all of the individual save and restore steps.
 
+=== Avoiding Two-phase Initialization ===
+
+If a directed graph of the data dependences has no cycles,
+then it can be serialized in an order such that when it is deserialized,
+all of the referenced data will exist before it is needed.
+That requirement, we assert, holds for anything in the Chimera2 core.
+And we can detect when it is violated,
+and report to the user what the offending toolor tools are.
+
+==== Saving Protocol ====
+
+1. Discovery
+  * All state is reachable from the session object
+  * The initial set objects to save in the session are the session's registered state attributes
+  * Objects to save are examined for referred to non-simple objects, and those objects are added to the set of savable objects, until all objects are examined
+    * These are the objects that need to be named symbolically
+    * Simple objects are ints, lists, dicts, etc.
+  * While examining savable objects:
+    * dependency graph is constructed
+    * the set of needed tools is constructed
+  * Detect "all" cycles, so user can take corrective action if there are cycles
+2. Serializing
+  * The list of needed tools and their session state versions
+  * The data in sorted order
+
+==== Restoring Protocol ====
+
+1. Get list of needed tools
+   * If installed tools are insufficient, allow user to install them
+     * If not installed, don't restore data from those tools, might fail
+2. Clear main session
+3. Restore into main session while blocking triggers
+
 === Tool Classes ===