feat: dotstorage hosts resolution layer #105
Conversation
vasco-santos
force-pushed
the
feat/dotstorage-hosts-resolution-layer
branch
from
afbd53c
to
e6f6207
Compare
| @@ -202,8 +204,24 @@ async function getFromDotstorage (request, cid, options = {}) { | |||
| response, | |||
| resolutionIdentifier: host | |||
| } | |||
| }), | |||
| ...env.cdnGateways.map(async (host) => { | |||
There was a problem hiding this comment.
This was not added as a GatewayRacer instance yet, but should be added in follow up.
At the moment, we have as part of this step (dotstorage cdn layer) performing requests to only if cached gateways (nftstorage.link asks w3s.link cache, and other way around). This means part of this race requires different headers, as well as non path resolution.
To use gateway racer now, we would need to add support there to specify headers per gateway target and to support path+subdomain resolution. This might not be needed, because we might go with CF Cache Reserve + custom hostname for nftstorage.link which would mean the onlyIfCachedHosts would not be needed anymore.
|
@vasco-santos freeway is ready and deployed to production. We just need NFT.Storage to write to R2 and for the indexes to also be written. It can be added to the race now. |
This PR adds to the dotstorage cdn resolution an array of CDN Gateways Race. This enables us to include freeway as part of our resolution before hitting first tier of IPFS gateways race.
Needs: