1281087 - Re-implement Bugzfeed-like change notification system using GraphQL Subscriptions

Status: RESOLVED WONTFIX

(bugzilla.mozilla.org :: API, task)

Description

[Kohei Yoshino [:kohei]]

The current Bugzfeed push notifications are simple yet serving well. However, the WebSockets API is apparently not a promising technology. It might be eventually replaced with the Web Push API that can also be used in service workers.

https://wiki.mozilla.org/BMO/ChangeNotificationSystem
https://daniel.haxx.se/blog/2016/06/15/no-websockets-over-http2/
https://serviceworke.rs/web-push.html

Comment 1

[Kohei Yoshino [:kohei]]

BMO will be based on the Mojolicious app framework soon (Bug 1455495). Web Push is not supported in Mojolicious yet, but server-sent events can be used instead [1][2], as per Dylan. It’s a simple API, no extra server is needed. Let’s try to use this to re-implement Bugzfeed so we can update bug threads real-time like BzDeck [3].

[1] https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events
[2] https://mojolicious.org/perldoc/Mojolicious/Guides/Cookbook#EventSource-web-service
[3] https://github.com/bzdeck/bzdeck/issues/42

In the future, I’d like to see a Web Push based notification API that works even after the browser tab is closed.

Comment 2

[Kohei Yoshino [:kohei]]

:dylan is going to experiment this with Mojo.

Comment 3

[Kohei Yoshino [:kohei]]

Update: WebSockets will work with HTTP/2 so it’s also an option (Bug 1434137). I guess the server-sent events API is simple yet enough though.

Comment 4

[Kohei Yoshino [:kohei]]

Looks like GraphQL supports subscriptions, usually implemented with WebSockets, so we don’t need a separate API for the new push notification system.

Comment 5

[:glob ✱]

We have no plans to do GraphQL in Bugzilla.