First version of explain. Creating a new parser was a wrong approach. Need to reimplement
This commit is contained in:
+3
-2
@@ -13,6 +13,7 @@
|
||||
- C : concept (with history management)
|
||||
- D : concept definitions (no history management)
|
||||
- R : executionContext ('R' stands for Result or ReturnValue, no history management)
|
||||
- V : variable (from pickle)
|
||||
|
||||
## How concepts are serialized ?
|
||||
- get the id of the concept
|
||||
@@ -35,9 +36,9 @@ structure of the serialisation:
|
||||
## Idea to manage ObjectSerializer
|
||||
Problem:
|
||||
During serialization, there is no issue. The match() method is the unique way to get the correct serialier.
|
||||
During the deserialisation, all Object serializer have type = '0' and version = 1.
|
||||
During the deserialisation, all Object serializer have type = 'O' and version = 1.
|
||||
So how to choose the correct one ?
|
||||
A possible solution will be to add the type of the object to deserialize to the saved stream
|
||||
--> SHA256 for every object. Too much data saved.
|
||||
The id is to let to inc the version automatically in the Serialiser (during the registration) and to keep the mapping within sdp.state
|
||||
|
||||
No, finally, I use a different char for each object type
|
||||
|
||||
Reference in New Issue
Block a user