Afaik The push sends a ping, the service worker awakes and does an http req
that receives the message and displays the notification without having to wake
up the full app.
For now I would add the payload till we migrate out of Google, or till this
gets high relevance.
On March 1, 2018 11:40:35 AM GMT-03:00, Stefan Sayer
<dmarc-noreply@xxxxxxxxxxxxx> wrote:
k@xxxxxxxxxxxxxxx wrote on 01.03.2018 15:33:
On 01/03/18 15:28, Nicolas Pace wrote:
The idea was to try not to send sensitive information throughHi Nico.
untrusted media...
Ok. So what is the needed or potential content of this payload then?
AFAIU, it can be implemented this way that the push notification only
wakes up the app, the app SIP REGISTERs on the server, and then gets
the incoming INVITE/MESSAGe which contains the caller; and then the
notification is shown to the user.
if the push notification should already display who is
calling/messaging or potentially the message text, then the server
needs to send this (sensitive) information in the payload.
So IIUC if we're using the generic service worker, then we need to use
the second option. Is that right, Emil?
many thanks!
Stefan
