ubuntu-push-devs team mailing list archive

[Lucio Torre <lucio.torre@xxxxxxxxxxxxx>]

Will this work on desktops? What happens if we use imei?

Notifications should be platform independent. Maybe we also want to keep
them consistent even if the hardware changes?

If the device id changes, we need to re create the queues, as this is like
having a new device. How do we tell the apps to re create the queues? Can
we assume the device id never changes? What happens with the old id if it
changes? Will we keep receiving and storing (for a ttl) messages for that
device?

Maybe we need to encapsulate some logic or provide documentation about the
pattern:

device_id = get_device_id()
stored_id = get_stored_device_id() # stored in app space, returns a null
value if nothing stored
if device_id != stored_id: # first time we run this or the device id changed
    token = create_queue()
    send_token_to_3rd_party_server(token)

maybe even some code to delete the old queues.

Lucio.


On Tue, Sep 10, 2013 at 5:03 PM, Ted Gould <ted@xxxxxxxxxx> wrote:

> **
> On Tue, 2013-09-10 at 14:33 -0300, Lucio Torre wrote:
>
> Today i learned that we dont have a device id anywhere in our stack. This
> means that we need to either have the push daemon create a device id when
> talking to the service or pass the list of channels it wants to listen to.
> If not, we will end up having devices without the app installed consuming
> messages for devices with the app.
>
>
> We discussed it on IRC, but just so folks on the list have context,
> Whoopsie generates a device ID that we use to track reports in
> http://errors.ubuntu.com  This is it's interface for those who need it.
>
>
> http://bazaar.launchpad.net/~ev/whoopsie-preferences/trunk/view/head:/src/whoopsie-preferences.xml
> Ted
>
> --
> Mailing list: https://launchpad.net/~ubuntu-push-devs
> Post to     : ubuntu-push-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-push-devs
> More help   : https://help.launchpad.net/ListHelp
>
>