Have a Node class with behavior that do not depends of graph existence, an OfflineNode class that inherit from Node and another OnlineNode class that also inherit from Node.
Have a Node class that contains a state property, of class NodeState. A property of NodeState is online, which is an object of the OnlineState class ( IsOffline and IsOnline classes inherit from OnlineState). A Node state can change (for example) from offline to online with method like Node.connect which call node.state.offline.connect.

After careful thought, I think I should implement an architecture where a Node can be Offline or Online, which change their behaviors and states. A Node which is Online is attached to a graph, and can be disconnected. An Offline Node is not attached to a graph and can be connected. Here, I have two choice: - Have a Node class with behavior that do not depends of graph existence, an OfflineNode class that inherit from Node and another OnlineNode class that also inherit from Node. - Have a Node class that contains a state property, of class NodeState. A property of NodeState is online, which is an object of the OnlineState class ( IsOffline and IsOnline classes inherit from OnlineState). A Node state can change (for example) from offline to online with method like Node.connect which call node.state.offline.connect.

linarphy commented

2026-04-26 05:16:02 +00:00

Author

Owner

I have chosen the last option, and have also applied it to Connection. Now updating tests.

linarphy referenced this issue from a commit

2026-04-26 06:21:02 +00:00

Update structure of Node and Connection classes (with better state management)

linarphy closed this issue

2026-04-26 06:21:02 +00:00