ipfs/kubo

Scale deadlines and timeouts off one variable

Open

#3,456 创建于 2016年12月1日

在 GitHub 查看
 (1 评论) (1 反应) (0 负责人)Go (13,906 star) (2,725 fork)batch import
help wantedtopic/libp2p

描述

IPFS is supposed to be interplanetary, with us setting timeouts for X minutes in multiple places it will be hard to get it running for interplanetary distances.

What I suggest is package with defined interface of timeouts, like connection timeout, time to live timeout and maybe "long" timeout. That then can be just change if someone wants to run IPFS on higher latency.

贡献者指南

技术栈
go
领域
backendperformance
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Go programmingUnderstanding of IPFS networking
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Search for timeout constants and deadline settings across the kubo codebase, for example in Go files that handle connections, request timeouts, and TTL. Identify all places where timeouts are hardcoded or configured. Then design a centralized timeout configuration package. The issue has not been updated since 2016, so it may require maintainer input to validate the approach.