Skip to content

Commit

Permalink
write alternatives section
Browse files Browse the repository at this point in the history
  • Loading branch information
hacdias committed Oct 20, 2022
1 parent 1fea39e commit e4cde04
Showing 1 changed file with 11 additions and 1 deletion.
12 changes: 11 additions & 1 deletion IPIP/0000-gateway-json-cbor-response-format.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,17 @@ is not strict enough:

### Alternatives

TODO
Introducing DAG-JSON, DAG-CBOR, JSON and CBOR in the HTTP Gateway allows for
a broader usage of the IPLD Data Model. If we do not introduce more IPLD
response formats in the gateway, the usage of IPFS is constricted to files
and directories represented by UnixFS (DAG-PB) codec. Therefore, it would keep
the IPLD potential locked due to an artificial barrier created by the gateways.

In addition, we could introduce only DAG-JSON and DAG-CBOR. However, not
supporting the generic variants, JSON and CBOR, would lead to poor UX. The
ability to retrieve DAG-JSON as `application/json` is an important step
for the interoperability of the HTTP Gateway with web browsers and other tools
that expect specific Content Types.

### Copyright

Expand Down

0 comments on commit e4cde04

Please sign in to comment.