[Aerogear-users] Registering and unregistering from Simple Push and Unified Push

[Sebastien Blanc]

On Wed, Jul 1, 2015 at 10:23 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi Mo,
>
> one note, we recently removed SimplePush from our Openshift Push
> cartridge, but more inline
>
> On Wed, Jul 1, 2015 at 9:31 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Hi,
>>
>> On Tue, Jun 30, 2015 at 7:30 PM, mo <michi.oshima at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> We use  OpenShift AeroGear Push Server Cartridge
>>> <https://github.com/aerogear/openshift-origin-cartridge-aerogear-push>
>>> .
>>>
>>> I've decided to register with simple-push and unified-push every time the
>>> user logs into our application.  Also to unregister from both
>>> unified-push
>>> and simple-push when they log out or browser closes.  Is this a good
>>> idea or
>>> bad idea?
>>>
>> Any reasons you are doing it this way ? AeroGear's SPS  JS implementation
>> will keep a mapping SPS <-> UPS in your localStorage, so when you register
>> again it will use this instead of creating a new installation.
>>
>
> Sebi, Is that really the case? is it really stored? and a reconnect works?
>
Yes and it should reconnect but tbh long time ago I tested that
https://github.com/aerogear/aerogear-js/blob/master/src/notifier/adapters/simplePush.js#L391-L418


>
> One big issue w/ SimplePush is, there is no notion of getting an ACK about
> if the channel is gone or not.
> Our server returns 200 for each PUT:
> https://wiki.mozilla.org/WebAPI/SimplePush/Protocol
>
> However, I recently noticed, that (regardless of the SimplePush Spec), the
> deployed MOZ server (wss://push.services.mozilla.com)  has a different
> notion:
> 200 -> OK (channel is active/registered/online)
> 202 -> Accept (chanel is known, but not yet online - scheduled for later
> delivery)
> 401/405 -> "errors" IMO sent when the PUT URL is invalid
>
> I think perhaps we need to revisit this in our Server impl.
>
>
> By registering/unregistering each time you will "pollute" the installation
>> table in UPS.
>>
>
> unregister will enure bogus installations (w/ eventually outdated
> channels) are no longer in the DB.
>
> simplepush is a bit different here - yes :-)
>
>
>>
>>
>>> Also, I've always wondered about the following comment in a sample code:
>>>
>>> "if it is the first registration, need to register the 'pushEndpoint'
>>> with
>>> the UnifiedPush server."
>>> <
>>> https://github.com/aerogear/aerogear-js-cookbook/blob/master/simplepush-unifiedpush-example/js/unifiedpush.js#L27-L28
>>> >
>>>
>> Once a SPS endpoint has been received it needs to register with the UPS
>> except when it has already be done (see previous comment)
>>
>>>
>>> Can somebody explain what is meant by the comment?  For example, what
>>> would
>>> count as a registration that's not the first?
>>>
>>> Thank you.
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://aerogear-users.1116366.n5.nabble.com/Registering-and-unregistering-from-Simple-Push-and-Unified-Push-tp86.html
>>> Sent from the aerogear-users mailing list archive at Nabble.com.
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150701/57534730/attachment-0001.html