| | 1 | Issues to resolve for online garbage collection: |
| | 2 | |
| | 3 | * The core issues is supporting online migration of objects to a different store or contiguous region |
| | 4 | * How would we handle generational GC to avoid moving all objects? |
| | 5 | * A 'gen' slot containing the generation variable? |
| | 6 | * A special tag in the serializer |
| | 7 | * A data store specific method for supporting access to the data for a given object? |
| | 8 | * Do we use multiple data stores and be data store agnostic, or let each data store |
| | 9 | implement its own policy? Problem is it has to interact with the metaprotocol to |
| | 10 | handle forwarding pointer - but perhaps that could be generic |
| | 11 | * Real-time or stop-and-copy? Transactions might help here as we could do incremental |
| | 12 | online garbage collection. Only problem is that persistent reference objects have |
| | 13 | non-protected internal slots like uid and sc. |
