@yasserf pointed out that the current serialization proposal serializes everything, which is wrong. He also seemed to intimate that the init() method was involved in how this is solved in CM when he said:
Sounds good. One thing worth mentioning is that CM doesn't do anything other than retrieve the map on stringify (unless you pass a map of data that you want to extract and it gets the intersection). My point was the init method allows each handler to figure out what data it needs from the initialisation map to set things to the desired state and ignores other data.
We need a solution, and while I can think of some from the top of my head, it make sense to try and capture what @yasserf already knows about this problem.
@yasserf pointed out that the current serialization proposal serializes everything, which is wrong. He also seemed to intimate that the
init()
method was involved in how this is solved in CM when he said:We need a solution, and while I can think of some from the top of my head, it make sense to try and capture what @yasserf already knows about this problem.