Allow event batching

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript
领域
api

调研方向

Start by reading the Push API specification around PushManager.subscribe and push event delivery; the issue does not name a file or test. Define how opt-in coalescing affects queued messages and event handling, then add specification text and tests that show a subscription with coalesce: true delivers a batch that developers can use to make one request and choose a notification.

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

描述

Right now, Safari fires push events sequentially, as in it fires the event, then waits for all the event.waitUntil calls to settle, before it fires the next one.

Assuming that events are generally processed like this:

  1. Look at push payload
  2. Show notification based on that payload

Or:

  1. Look at push payload
  2. Make network request for data
  3. Show notification based on payload + response

In cases where the device has a queue of push messages, it seems advantageous to batch these into a single event. This would allow developers to make a single network request, rather than a series of network requests, and be smart about the notification displayed, e.g. "You have 7 new messages".

There's prior art here with getCoalescedEvents.

This would need to be opt-in as part of pushManager.subscribe, eg:

await serviceWorkerRegistration.pushManager.subscribe({
  coalesce: true,
});
主要语言
HTML
星标
158
派生
43
平均合并
2 天 6 小时
30 天内合并 PR
2

环境准备

从这里开始

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

w3c/push-api 的其他 Issue

查看 w3c/push-api 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

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