IPIP-356: IPFSClient API

[markg85]

Draft for sure!

This spec is intended to specify how a "ipfsclient" works. It relies on 3 different specs:

1. IPIP-0280 (gateways file)
2. IPIP-0000 (multi gateway client. This spec defines how gateways are determined to be used and use them)
3. IPIP-0000 (using gateways. This spec defines how an application can find and use gateways)

The missing specs will be on github later. Will update this message when they are online.

[Winterhuman]

Maybe the doc should mention Cache-Control: only-if-cached (https://github.com/ipfs/kubo/pull/9082) as the recommended way to contact gateways initially? Sending requests to multiple gateways seems wasteful if a gateway in the list already has the data and can begin sending content immediately

[markg85]

Maybe the doc should mention Cache-Control: only-if-cached (ipfs/kubo#9082) as the recommended way to contact gateways initially? Sending requests to multiple gateways seems wasteful if a gateway in the list already has the data and can begin sending content immediately

Perhaps. But that would be the job of https://github.com/ipfs/specs/pull/359 :) You couldn't have known, that spec wasn't on github yet when you made the comment.

This spec will do no gateway managing on it's own! Or in different terms, the way the function required Error ipfs(&Url ipfs_url); would be implemented would be through following https://github.com/ipfs/specs/pull/359.

Technically in terms of code it will all live in the same repository. Spec wise it's separated.