{"version":"2.1.248","anchor":"sync-objects-addressed-by-full-path-transport-simplified-to-","canonical_anchor":"sync-objects-addressed-by-full-path-transport-simplified-to-","heading":"Sync objects addressed by full path, transport simplified to one client","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/sync-objects-addressed-by-full-path-transport-simplified-to-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Sync objects addressed by full path, transport simplified to one client\n\nSynced objects now use full paths and always publish through one client.\n\n**What**\n\nSynced objects are now identified by a full directory-plus-suffix path rather than a bare name, and outbound publishing always goes through the direct client with a worker-side marker and optional stall and restart-pause timings. The older fallbacks (size-threshold direct upload, an over-cap row write, and an etag memo on rejected requests) are gone from this path.\n\n**Evidence**\n\n`a sync object is named by a lowercase-hex sha256`\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}