Add ability to "ping" a receiver to help with discovery
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
调研方向
The issue describes a receiver discovery feature that the current protocol cannot support and defers it to v2. Start by reading the protocol’s receiver discovery and authentication sections to understand the current limits. Done means specifying how a sender can ping a receiver and how the receiver signals itself; the issue names no files or tests.
由索引模型根据 Issue 内容生成。
描述
In Berlin, we discussed the ability to "ping" a display to help users disambiguate between multiple receivers (perhaps with similar names) that may show up in a list of named receivers. This would be useful in a meeting room with multiple displays, for example.
This is not currently not possible given the way the protocol is specified today, so we agreed to track this as a v2 issue. The user workflow in the time being will be to leverage the authentication UI (such as the receiver showing a pin) to verify that the receiver chosen was the correct one.
- 主要语言
- Bikeshed
- 星标
- 115
- 派生
- 21
- 平均合并
- 5 小时 2 分钟
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
w3c/openscreenprotocol 的其他 Issue
-
难度 5/5 一周以上 新手友好度 18/100
w3c/openscreenprotocol#380 ·
-
osp-application
难度 5/5 一周以上 新手友好度 35/100
w3c/openscreenprotocol#377 ·
-
难度 4/5 3-5 天 新手友好度 38/100
w3c/openscreenprotocol#376 ·
-
osp-application
难度 2/5 1-3 小时 新手友好度 55/100
w3c/openscreenprotocol#375 ·
-
osp-application question
难度 5/5 一周以上 新手友好度 30/100
w3c/openscreenprotocol#374 ·