<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 1, 2015 at 10:23 AM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi Mo,<div><br></div><div>one note, we recently removed SimplePush from our Openshift Push cartridge, but more inline<br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Jul 1, 2015 at 9:31 AM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi,<div class="gmail_extra"><br><div class="gmail_quote"><span>On Tue, Jun 30, 2015 at 7:30 PM, mo <span dir="ltr"><<a href="mailto:michi.oshima@gmail.com" target="_blank">michi.oshima@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<br>
<br>
We use OpenShift AeroGear Push Server Cartridge<br>
<<a href="https://github.com/aerogear/openshift-origin-cartridge-aerogear-push" rel="noreferrer" target="_blank">https://github.com/aerogear/openshift-origin-cartridge-aerogear-push</a>> .<br>
<br>
I've decided to register with simple-push and unified-push every time the<br>
user logs into our application. Also to unregister from both unified-push<br>
and simple-push when they log out or browser closes. Is this a good idea or<br>
bad idea?<br></blockquote></span><div>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.</div></div></div></div></blockquote><div><br></div></span><div>Sebi, Is that really the case? is it really stored? and a reconnect works?</div></div></div></div></div></blockquote><div>Yes and it should reconnect but tbh long time ago I tested that </div><div><a href="https://github.com/aerogear/aerogear-js/blob/master/src/notifier/adapters/simplePush.js#L391-L418">https://github.com/aerogear/aerogear-js/blob/master/src/notifier/adapters/simplePush.js#L391-L418</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>One big issue w/ SimplePush is, there is no notion of getting an ACK about if the channel is gone or not.</div><div>Our server returns 200 for each PUT:</div><div><a href="https://wiki.mozilla.org/WebAPI/SimplePush/Protocol" target="_blank">https://wiki.mozilla.org/WebAPI/SimplePush/Protocol</a><br></div><div><br></div><div>However, I recently noticed, that (regardless of the SimplePush Spec), the deployed MOZ server (wss://<a href="http://push.services.mozilla.com" target="_blank">push.services.mozilla.com</a>) has a different notion:</div><div>200 -> OK (channel is active/registered/online)</div><div>202 -> Accept (chanel is known, but not yet online - scheduled for later delivery)</div><div>401/405 -> "errors" IMO sent when the PUT URL is invalid</div><div><br></div><div>I think perhaps we need to revisit this in our Server impl.</div><span class=""><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>By registering/unregistering each time you will "pollute" the installation table in UPS.</div></div></div></div></blockquote><div><br></div></span><div>unregister will enure bogus installations (w/ eventually outdated channels) are no longer in the DB.</div><div><br></div><div>simplepush is a bit different here - yes :-)</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Also, I've always wondered about the following comment in a sample code:<br>
<br>
"if it is the first registration, need to register the 'pushEndpoint' with<br>
the UnifiedPush server."<br>
<<a href="https://github.com/aerogear/aerogear-js-cookbook/blob/master/simplepush-unifiedpush-example/js/unifiedpush.js#L27-L28" rel="noreferrer" target="_blank">https://github.com/aerogear/aerogear-js-cookbook/blob/master/simplepush-unifiedpush-example/js/unifiedpush.js#L27-L28</a>><br></blockquote></span><div>Once a SPS endpoint has been received it needs to register with the UPS except when it has already be done (see previous comment) </div><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Can somebody explain what is meant by the comment? For example, what would<br>
count as a registration that's not the first?<br>
<br>
Thank you.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://aerogear-users.1116366.n5.nabble.com/Registering-and-unregistering-from-Simple-Push-and-Unified-Push-tp86.html" rel="noreferrer" target="_blank">http://aerogear-users.1116366.n5.nabble.com/Registering-and-unregistering-from-Simple-Push-and-Unified-Push-tp86.html</a><br>
Sent from the aerogear-users mailing list archive at Nabble.com.<br>
_______________________________________________<br>
Aerogear-users mailing list<br>
<a href="mailto:Aerogear-users@lists.jboss.org" target="_blank">Aerogear-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-users" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-users</a><br>
</blockquote></span></div><br></div></div>
<br>_______________________________________________<br>
Aerogear-users mailing list<br>
<a href="mailto:Aerogear-users@lists.jboss.org" target="_blank">Aerogear-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-users" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-users</a><br>
<br></blockquote></span></div><span class=""><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</font></span></div></div></div>
<br>_______________________________________________<br>
Aerogear-users mailing list<br>
<a href="mailto:Aerogear-users@lists.jboss.org">Aerogear-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-users" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-users</a><br>
<br></blockquote></div><br></div></div>