On 14/04/2016 8:26 AM, Ryan Kelly wrote:
On 8/04/2016 04:03, Edouard Oger wrote:
Hello everyone,
The Sync team is currently trying to figure out how to send "device
connected" notifications to clients (see
https://bugzilla.mozilla.org/show_bug.cgi?id=3D1201335).
We would like to use the push API to send these notifications to other
FXA (~= Sync) clients.
The goal would be to store another endpoint on the fxa-auth-server for
Sync related notifications.
We would -probably- use data payloads in order to send different types
of messages.
This new endpoint could also solve "Add push support for remote
disconnect of devices"
(https://github.com/mozilla/fxa-auth-server/issues/1139), with a "Device
changed" endpoint and the data payload would state "removal"/"added" and
the device GUID.
Another good solution would be to use multiple endpoints and send empty
payloads.
We would also need tty > 0 pushs. Until the infrastructure is ready, we
wouldn't mind dealing with short ttys but in the future we would need
longer ttys.
We would love to hear your thoughts on this.
Sorry to leave this unanswered for so long!
I'm curious what the advantage would be of using an additional push
endpoint for this, versus just sending message payloads over the
existing push channel. We have a handful of work on the FxA side that
would also benefit from message payloads.
I suggested Edouard send this mail as I couldn't recall what consensus
we reached before. I *thought* we decided on various end-points given
they were cheap and payloads were up-in-the-air - but as you mention, we
probably can have payloads now, especially as Kit tells me Chrome has
shipped with them, so has basically committed to the crypto they will
(and we should) use.
IOW, we see both techniques as able to provide the functionality we want
but were unsure about what approach to take. IIRC Edouard preferred the
"use the payload" option and given that sounds viable and non
controversial, let's go with that!
Thanks,
Mark
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
