WebSeed specifications

未关闭
#444 1 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞

调研方向

从 BEP-19、RFC 7233、IPIP402 和链接的规范 PR #445 开始,然后审查 issue #444 中尚未完成的里程碑。完成意味着 webseed 用例、信令语义和所需规范已经达成一致并完成文档记录;目前,该 issue 的大多数实现细节仍为 TODO。

由索引模型根据 Issue 内容生成。

描述

kind/enhancement meta

This is a meta issue discussing required features to enable webseed like features for the IPFS network.

A webseed is qualified as a server:

  • Server that implements a version of the HTTP protocol. Or protocols with equivalent GET semantics. (like FTP)
  • Is able to serve static files.
  • Supports RFC 7233 bytes HTTP Range request on such files. Or protocols with equivalent ranging semantics. (like FTP)
  • Does not run IPFS aware pieces of code.
  • And finally can be used by IPFS clients to download content without compromising on the IPFS features (extensible content addressed incremental verification).

The endgame here would be to upload some file to such server which would contain both the merkle dag cryptographic proofs and an index which would allow clients to implement O(log n) seeking and random read behaviors.
Here for unixfs we have 2½ usecases which are useful to separate:

  • 1. IPFS proofs and index packed together with the leaves node. This mode would be blind to content of the blocks and could work with any IPFS application.
    Potential applications target IPFS native applications which want to leverage extensive HTTP compatible storage services which do not understand IPFS.
  • 2. IPFS proofs and index stored separately from the de-serialized leaves of the tree. This is usefull for applications which also want to serve their content over non IPFS means, this allows to reuse existing non IPFS architectures and have IPFS clients download the same files as non ipfs clients for the raw-leaves of the file.
  • 2½. Similar as point 2 however it allows for using non webseeds (servers that run IPFS aware code) for downloading the proofs.
    This also include usecases where the proofs are packed into an archive and shared OOB (see .torrent files for an example).

I can think of at least one other possible implementation (one plain file per block) but I am not including it here due to dubious value, could be added if this interest peoples, this could also be implemented without updating the spec using IPIP402 and very minimal header rewriting.

Milestones

2½

2

  • TODO

1

  • TODO
主要语言
HTML
星标
1.2k
派生
250
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ipfs/specs 的其他 Issue

查看 ipfs/specs 的全部 Issue

相似的 Issue

更多 Distributed Systems Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。