You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In RFML, we've used UUIDs that get associated with a node for the ID of that node. We should either trim that down (associate an Int with a node instead) or be able to (repeatably) generate a unique set of IDs in some fashion for a given tree
The text was updated successfully, but these errors were encountered:
The current thinking on this is to provide - via a very simple algorithm - a means of identifying nodes. This way the client and server can pass information back and forth about portions of the tree without passing indexes around in a JSON structure that we'd like to keep as thin as possible. Perhaps:
In RFML, we've used
UUID
s that get associated with a node for the ID of that node. We should either trim that down (associate anInt
with a node instead) or be able to (repeatably) generate a unique set of IDs in some fashion for a given treeThe text was updated successfully, but these errors were encountered: