<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">+1<br><div><div>On Aug 28, 2013, at 10:39 AM, Kris Borchers <<a href="mailto:kborcher@redhat.com">kborcher@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="auto"><div><br></div><div><br>On Aug 28, 2013, at 9:36, Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">+1 Sounds good and I've moved the following task into SimplePush 0.9.0 for the clean up of channelIds:<div><a href="https://issues.jboss.org/browse/AGPUSH-204">https://issues.jboss.org/browse/AGPUSH-204</a><br></div></div></blockquote><div><br></div>Perfect, thanks!<br><blockquote type="cite"><div dir="ltr">
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 28 August 2013 16:32, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div><div class="h5">
<div>On 08/28/2013 10:12 AM, Kris Borchers
wrote:<br>
</div>
<blockquote type="cite">
As I work more and more toward aligning with the API spec laid out
by Mozilla for SimplePush, I find myself needing to make a major
change to the way we have implemented channel registrations.
Basically what I have found is that our storage and reuse of
channels between app restart/refresh, though meant to be an
improvement to performance, is causing more issues than it's
solving.
<div><br>
</div>
<div>The Proposal</div>
<div>I would like to only persist the user agent id (UAID) in
storage and only keep the channel registrations in memory while
the app is running. Each time the app starts up, the workflow
would be:</div>
<div><br>
</div>
<div>
<ul>
<li>First Start</li>
<ol>
<li>Client Hello => Server</li>
<li>Server Ack => Client</li>
<li>Client 1 or more channel registrations => Server</li>
<li>Server stores channel and sends pushEndpoint =>
Client</li>
<li>Client registers endpont => App Server or UP Server</li>
<li>Push messages abound</li>
</ol>
<li>Restart / Refresh</li>
<ol>
<li>Client Hello => Server</li>
<li>Server recognizes UAID and since no channels were
included in Hello, all existing channels are removed as
per the spec and sends Ack => Client</li>
<li>Client 1 or more channel registrations => Server</li>
<li>Server stores channel and sends pushEndpoint =>
Client</li>
<li>Client registers endpont => App Server or UP Server</li>
<li>Push messages abound</li>
</ol>
</ul>
<div><br>
</div>
</div>
<div>The only possible downside I see here is there will be
slightly more chatter over the network since the registrations
will happen every time the app loads. There should be no
performance decrease and may see a performance boost since we
will be eliminating a number of synchronous calls into
localStorage. The main benefit is that this will allow us to
almost completely synchronize our API with Mozilla's which would
then allow for immediate use of one of our apps as a web app and
Firefox OS app with NO modifications.</div>
<div><br>
</div>
<div>Any thoughts?</div>
</blockquote></div></div>
Sounds good. While not 100% related rerunning registration on app
load is something Google suggests for GCM.<div class="im"><br>
<blockquote type="cite">
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
aerogear-dev mailing list
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</div></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>
</blockquote><blockquote type="cite"><span>_______________________________________________</span><br><span>aerogear-dev mailing list</span><br><span><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></span></blockquote></div>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></body></html>