{
  "slug": "foreign-object-table",
  "term": "Foreign object table",
  "aliases": [
    "FOT (Twizzler)"
  ],
  "definition": "A foreign object table is per-object metadata that resolves a stored persistent pointer's table index to an external object's identity.",
  "note": "In the Twizzler object-space proposal, a persistent pointer contains a table index and an offset. Index zero refers inside the containing object; positive indexes select that object's foreign object table. The indirection keeps pointer size separate from the size of a global object identifier. [hotstorage19]\n\nAn illustrative consequence: suppose object A's entry 2 names X, while object B's entry 2 names Y. The same index-and-offset pair (2, 64) then denotes X at offset 64 in A, but Y at offset 64 in B. Copying that pair alone is not a context-preserving transfer. This is a schematic deduction, not a measured Twizzler execution or an ABI encoding example.\n\nDo not confuse the global object space with the local logical object space: the latter abstracts physical mappings for the active working set and need not itself persist. [hotstorage19]",
  "status": "research",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-16",
  "related": [
    "twizzler"
  ],
  "citations": [
    {
      "id": "hotstorage19",
      "label": "Object space, HotStorage 2019",
      "title": "Bittman, Alvaro, Long and Miller. A Tale of Two Abstractions: The Case for Object Space. HotStorage 2019, updated paper; section 2.",
      "url": "https://www.usenix.org/system/files/hotstorage19-paper-bittman-update.pdf",
      "accessed": "2026-11-16"
    }
  ],
  "provenance": [
    "The A/B/X/Y example is original explanatory reasoning from the published per-object lookup rule; it does not model deletion, access checks or recovery."
  ]
}
