Comment 5 for bug 1596119

Hans, I don't understand how that could be the case. Why would the conductor need to forward port it? All the nodes that the object should be sent to (or loaded in) should be happy to see a 1.1 object if they support up to 1.2.

On the other hand, if conductors were older than other nodes, a new object could be stored in the database which would confuse the conductor when it went to deserialize it.

In short, there should be no problem storing older objects in the database as long as we can still support their major version. It should be identical to receiving that older object over RPC from an older node.