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
First intuition for implementation:
Server should have an UEIDSupplier resource. It is responsible to generate new UEID-s.
It should store the "highest reserved ID+1" which will be initially 0. When an entity is being deleted that has an UEID, this UEIDSupplier should be notified, because it has to free the deleted UEID.
In this case the freed UEID should be stored in a sorted collection to know that this UEID can be reused.
Downside:
When an entity dies, UEIDSupplier must be manually notified to free its UEID
UEID should contain a unique u64 ID
The text was updated successfully, but these errors were encountered: