Superalgos - Clones

Clones

Summary: The clone feature is designed to produce copies of data structures when you need to replicate structures of nodes and expect the copies to behave similarly to the original.

Introduction

We will analyze the case of clones under the same lens we analyzed how backups work: we will study how clones treat outgoing, incoming and internal references.

Note: Unlike backups, clones behave in the same way independently of the existence of the original structure of nodes in the workspace, therefore, we will not make such distinction in the following paragraphs.

Outgoing References

Outgoing references are kept intact.

Pretty much like with backups, a clone preserves outgoing references.

The same example as with backups apply: cloning a running a produces a copy of the with the maintaining the reference to the process, maintaining the reference to the corresponding , and the keeping the reference to the hierarchy.

Incoming References

Incoming references are discarded.

Let’s go back to the example of a , like we did when exploring backups:

The capture above shows that restoring a clone of a trading system does not restore incoming references, even when the original structure of nodes is deleted before restoration.

Internal References

Internal references are kept intact.

Going back to the shapes node example, the capture below shows how restoring a clone keeps internal references intact:

Conclusion

The clone feature is designed to produce copies of data structures when you need to replicate nodes and expect the copies to behave similarly to the original.

Productivity Tools — TOC

You just read page 2 in the topic.

1. Backups

2. Clones

3. Shares

4. Screen Capture and Sharing

Superalgos is an open-source project run and governed by a decentralized community of contributors. There is no legal entity behind the project. Our body of work lives on the Internet.