Skip to content

Commit

Permalink
Merge pull request #372 from ipfs/feat/remove-reframe
Browse files Browse the repository at this point in the history
feat: remove reframe
  • Loading branch information
lidel authored Jan 31, 2023
2 parents 9462fd2 + 28954b5 commit 34aea14
Show file tree
Hide file tree
Showing 7 changed files with 2 additions and 533 deletions.
3 changes: 1 addition & 2 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
Expand Up @@ -10,5 +10,4 @@ IPIP/ @ipfs/specs-stewards
# review when someone opens a pull request that modifies area of their
# interest.

http-gateways/ @lidel
reframe/*HTTP* @lidel
http-gateways/ @lidel
1 change: 0 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,6 @@ The specs contained in this and related repositories are:
- [Other IPFS Overviews](/overviews) - quick overviews of the various parts of IPFS
- **User Interface (aka Public APIs):**
- [HTTP Gateways](./http-gateways/) - implementation agnostic interfaces for accessing content-addressed data over HTTP
- [REFRAME](./reframe/) - protocol designed for request-response messages that is sufficiently generic and extensible to evolve over time as new needs for it arise
- IPFS implementations may provide additional interfaces, for example:
- [Legacy HTTP RPC API exposed by Kubo (go-ipfs)](https://docs.ipfs.io/reference/http/api/)
- [Programmatic Core API for JavaScript](https://github.com/ipfs/js-ipfs/tree/master/docs/core-api#readme)
Expand Down
3 changes: 1 addition & 2 deletions ipns/IPNS.md
Original file line number Diff line number Diff line change
Expand Up @@ -250,8 +250,7 @@ Once the record is created, it is ready to be spread through the network. This w

The means of distribution are left unspecified. Implementations MAY choose to
publish signed record using multiple routing systems, such as
[libp2p Kademlia DHT](https://github.com/libp2p/specs/tree/master/kad-dht),
[PubSub topic](./IPNS_PUBSUB.md), or a [Reframe endpoint](../reframe/) (see [Routing record](#routing-record)).
[libp2p Kademlia DHT](https://github.com/libp2p/specs/tree/master/kad-dht) or [PubSub](./IPNS_PUBSUB.md) (see [Routing record](#routing-record)).

On the other side, each peer must be able to get a record published by another node. It only needs to have the unique identifier used to publish the record to the network. Taking into account the routing system being used, we may obtain a set of occurrences of the record from the network. In this case, records can be compared using the sequence number, in order to obtain the most recent one.

Expand Down
5 changes: 0 additions & 5 deletions reframe/README.md

This file was deleted.

104 changes: 0 additions & 104 deletions reframe/REFRAME_HTTP_TRANSPORT.md

This file was deleted.

Loading

0 comments on commit 34aea14

Please sign in to comment.