Reconsider the message length requirement

未关闭
  • 哪里不对？
#374 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
javascript
领域
networking

调研方向

The issue discusses the protocol’s 1GB message length requirement and its compatibility with RTCDataChannel and receiver memory limits, but it does not name a specification file or test. Start by locating the requirement in the protocol specification and checking what limits the relevant transports impose. Done means proposing and agreeing on a lower maximum message size; the issue does not provide enough information to choose one.

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

描述

osp-application question

The message length requirement of 1GB was proposed as the maximum that could theoretically be supported by a CBOR + Javascript + WebTransport + QUIC stack.

However, there are a couple of problems:

  1. RTCDataChannel has a much lower practical limit, possibly as low as 64KB.
  2. There's no guarantee that the receiver has enough RAM to decode, store, and process the message.

So a lower value seems advisable, but how low?

主要语言
Bikeshed
星标
115
派生
21
平均合并
5 小时 2 分钟
30 天内合并 PR
2

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

w3c/openscreenprotocol 的其他 Issue

查看 w3c/openscreenprotocol 的全部 Issue

相似的 Issue

更多 Networking Issue

把新 issue 发到你的邮箱

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