[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$faMYKXHRT7V4Eg1gtnTp6s6Mlw_nZ-2bzipO9zUQhB1s":3},{"item":4,"related":44},{"id":5,"type":6,"title":7,"slug":8,"summary":9,"body":10,"coverUrl":11,"productScreenshots":12,"productLinks":13,"authorName":14,"authorUrl":15,"authorSubject":16,"category":17,"tags":22,"sourceLabel":35,"sourceName":35,"sourceUrl":36,"status":37,"seoTitle":7,"seoDescription":9,"canonicalUrl":38,"isFeatured":39,"sno":40,"sortOrder":41,"publishedAt":42,"updatedAt":43,"createdAt":43},"1cc0b372-1c09-4718-b058-75e8eccae8df","article","QUIC DATAGRAM：有些实时数据为什么不值得重传？","quic-datagram-unreliable-transport","QUIC DATAGRAM 扩展让应用在加密 QUIC 连接中传递不保证重传、也不保证有序的短消息，适合过期即无用的实时数据。它仍受拥塞控制，也需要双方协商支持；本文用语音与游戏状态说明取舍。","聊天、在线游戏和实时协作里，有些数据包如果没赶上时间，补发反而没有意义：语音通话里两秒前的音频已经过时，游戏角色刚才的位置也许早就更新。可靠传输会努力重传丢失数据，但这份可靠性可能变成延迟。QUIC DATAGRAM 扩展，就是让应用在 QUIC 连接里发送“不保证重传”的数据报。\n\n## 同一条连接里，可靠流和易失消息并存\n\n普通 QUIC 流提供可靠、有序的字节流，适合网页文本、文件和请求响应。DATAGRAM 帧则允许应用发送边界清楚的消息；若数据包丢失，协议不会像可靠流那样要求把它补回来。接收方可能收到消息，也可能收不到，应用需要自行判断这是否可接受。\n\n这有点像快递与现场直播的区别。合同原件丢了必须补寄；直播里某一帧丢了，下一帧很快就来，再补旧画面只会拖慢观看。开发者可在同一 QUIC 连接中把需要可靠传输的数据放进流，把过期即无用的状态更新放进 DATAGRAM。\n\n## 不重传，不等于没有规则\n\nDATAGRAM 仍运行在 QUIC 连接之上，保留加密与连接上下文，并受到 QUIC 拥塞控制约束。网络拥塞时，发送端仍应适当降低发送速率；“不可靠”只表示协议不保证丢包后重传或按序交付，不表示可以无限制灌入数据。\n\n两端还必须都支持并协商启用相应扩展。应用要自行处理消息大小、丢失、过期、去重或必要的纠错。若开发者把本来必须可靠保存的数据放进不可靠消息，协议不会替业务补救。\n\n因此，QUIC DATAGRAM 不是“更快的 UDP 替代品”，而是一种在加密、拥塞受控的 QUIC 会话中承载短消息的补充方式。它适合对时效敏感、能容忍少量丢失的数据；不适合必须完整到达的账单、文件或指令。选择可靠还是不可靠，最终应由数据过期后的价值决定。\n\n来源：[IETF RFC 9221：An Unreliable Datagram Extension to QUIC](https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9221.html)","\u002Fuploads\u002F2026-10-17\u002Fd0072eed-769d-4cdb-9bd7-7e2eedf7bbda.jpg",[],[],"Foundit","https:\u002F\u002Ffoundit.cn","foundit-ai-editorial",{"id":18,"name":19,"slug":20,"description":21},"6179d3b6-dc34-4483-9ded-3cd9f1b37a47","科普","abbreviation","介绍各领域新兴概念",[23,27,31],{"id":24,"name":25,"slug":26},"7c76bfc2-f80f-4ee0-a95d-27bd8708b434","技术","slug",{"id":28,"name":29,"slug":30},"a202d639-99a6-488a-a712-4d4c6ffd7e15","开发","dev",{"id":32,"name":33,"slug":34},"4c2bbea6-eab7-40a8-8447-1de478ff7749","分析","analyse","IETF RFC 9221","https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9221.html","published",null,false,43,0,"2026-10-17T00:00:00.000Z","2026-10-17T03:08:42.958Z",[45,54,62],{"id":46,"type":6,"title":47,"slug":48,"summary":49,"coverUrl":50,"authorName":14,"sno":51,"publishedAt":52,"createdAt":53},"9ccde95c-d754-4808-91f7-488f392e3eeb","你的品牌在AI眼里到底存不存在？这套系统说了算","automated-geo-monitoring-system","靠手动抽查来验证GEO效果，本质上是在跟概率玩游戏。赢一次，不代表能一直赢。","\u002Fuploads\u002F2026-08-07\u002Fdf111c0d-f14a-4b2a-8347-141e96b71654.jpg",1,"2026-08-07T00:00:00.000Z","2026-08-07T04:31:30.843Z",{"id":55,"type":6,"title":56,"slug":57,"summary":58,"coverUrl":59,"authorName":14,"sno":60,"publishedAt":42,"createdAt":61},"9865c835-21fc-4f74-b154-19c054173557","fscrypt：只给手机里的某个文件夹加密，系统怎么做到？","linux-fscrypt-file-based-encryption","Linux fscrypt 在支持的文件系统中为目录树、文件内容和文件名提供文件级加密。它与整盘加密保护的范围不同，也不会隐藏所有文件系统元数据；本文从解锁密钥说到备份与恢复的边界。","\u002Fuploads\u002F2026-10-17\u002Fdec803fe-0da3-4a9e-8ffc-47427cf599d6.jpg",41,"2026-10-17T03:08:37.641Z",{"id":63,"type":6,"title":64,"slug":65,"summary":66,"coverUrl":67,"authorName":14,"sno":68,"publishedAt":69,"createdAt":70},"56d3ebcb-170a-4f96-9134-ae85fb65542b","DANE\u002FTLSA：DNSSEC 能否帮助验证网站的 TLS 证书？","dane-tlsa-dnssec-tls-authentication","DANE 使用 DNS 中的 TLSA 记录发布与 TLS 服务证书或公钥相关的约束，并依赖 DNSSEC 验证记录来源。本文解释它如何补充信任路径，以及为什么它不等于所有网站都能抛弃 CA。","\u002Fuploads\u002F2026-10-13\u002F8c7d9bf5-62c6-47d4-b8eb-c4db7a21fa61.jpg",42,"2026-10-13T00:00:00.000Z","2026-10-13T02:13:55.563Z"]