<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 28, 2013 at 4:40 PM, Apostolos Emmanouilidis <span dir="ltr">&lt;<a href="mailto:aemmanou@redhat.com" target="_blank">aemmanou@redhat.com</a>&gt;</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"><u></u>


  
  

<div>
Thanks Matthias<br>
<br>
I was wondering how the feedback service could be handled in a consistent way since GCM Sender.send method is synchronous but the corresponding method on APN is asynchronous. Adding a send notifications page might have as a consequence to persist the GCM responses until the &quot;tidy-up&quot; procedure is executed. <br>

</div></blockquote><div><br></div><div style>Once the Unified Push server receives an HTTP request to send messages to APNs/GCM, the payload is submitted to jobs (CDI events, and async (EJB) receviers), for exactly that reason. All the HTTP endpoint does is, sending a 200 response &quot;200: Job submitted&quot; (There is no real guarantee anyways. Phone cloud be airplane mode, and app deinstalled while in the plane, etc).</div>
<div><br></div><div><br></div><div style>Regarding GCM, in that &quot;job&quot;:  once the gcm.send() has been fully executed, we can read the MulticastResult;</div><div><br></div><div style>The APNs &quot;feedback&quot; will be still a scheduled thing: every n hours</div>
<div style><br></div><div style>At least initially </div><div><br></div><div><br></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><div><div>
<br>
On Tue, 2013-05-28 at 16:02 +0200, Matthias Wessendorf wrote:
<blockquote type="CITE">
    <br>
</blockquote>
<blockquote type="CITE">
    <br>
    <br>
</blockquote>
<blockquote type="CITE">
    On Tue, May 28, 2013 at 3:55 PM, Matthias Wessendorf &lt;<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>&gt; wrote:
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        On Tue, May 28, 2013 at 3:42 PM, Apostolos Emmanouilidis &lt;<a href="mailto:aemmanou@redhat.com" target="_blank">aemmanou@redhat.com</a>&gt; wrote:<br>
        <blockquote>
            In my opinion, adding a UI to send notification message will make the<br>
            Admin UI quite complex. If the users are able to send notification<br>
            messages from the UI they should also be able to receive the feedback<br>
            information from the Push Notification servers.
        </blockquote>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        I agree, since I am also not a fan of sending messages from the UI. However folks keep asking, 
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        so I asked for that JIRA. this will, for sure, not be included in the first release;
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
         
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <blockquote>
            <br>
            For example Apple mentions that &quot;APNs has a feedback service that<br>
            maintains a per-application list of devices for which there were<br>
            failed-delivery attempts (that is, APNs was unable to deliver a push<br>
            notification to an application on a device). Periodically, the provider<br>
            should connect with the feedback service to see what devices have<br>
            persistent failures so that it can refrain from sending push<br>
            notifications to them.&quot;
        </blockquote>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        Not needed.
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        We have a ticket that we need a &quot;scheduled&quot; job to receive invalid from the network(s), in order to perform the &quot;tidy-up&quot;:
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <a href="https://issues.jboss.org/browse/AGPUSH-45" target="_blank">https://issues.jboss.org/browse/AGPUSH-45</a><br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        Even _if_ we would do the SEND from the UI, the job (AGPUSH-45) would still be the only one, responsible for that &quot;tidy-up&quot;.
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        No need to stick this &quot;request feedback&quot; into the UI
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <br>
    <br>
</blockquote>
<blockquote type="CITE">
    Besides a simple field to schedule the actual &quot;interval&quot; :)
</blockquote>
<blockquote type="CITE">
     
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
         
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <blockquote>
            <br>
            This means that extra functionality will be required, like the<br>
            synchronization of the tokens. The &quot;inactive&quot; tokens should be removed<br>
            or marked as &quot;token to be deleted&quot; and let the admin user decide whether<br>
            they will be deleted or not.
        </blockquote>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <blockquote>
            <br>
            <br>
            On Fri, 2013-05-24 at 10:18 +0200, Matthias Wessendorf wrote:<br>
            &gt; perfect, thanks!<br>
            &gt;<br>
            &gt;<br>
            &gt; On Fri, May 24, 2013 at 9:54 AM, Corinne Krych<br>
            &gt; &lt;<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>&gt; wrote:<br>
            &gt;         <a href="https://issues.jboss.org/browse/AGPUSH-38" target="_blank">https://issues.jboss.org/browse/AGPUSH-38</a><br>
            &gt;<br>
            &gt;<br>
            &gt;         for this (optional) 1.2.0 feature<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;         On 24 May 2013 08:01, Matthias Wessendorf &lt;<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>&gt;<br>
            &gt;         wrote:<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;                 On Fri, May 24, 2013 at 12:12 AM, Corinne Krych<br>
            &gt;                 &lt;<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>&gt; wrote:<br>
            &gt;                         Will the adminui provides UI to send<br>
            &gt;                         notification message?<br>
            &gt;                         It could be useful for testing purpose.<br>
            &gt;<br>
            &gt;<br>
            &gt;                 Not sure, if we do it for August, but can u file a<br>
            &gt;                 JIRA ?<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;                         Or another use case could be to send automatic<br>
            &gt;                         - rule triggerred - messages.<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;                 Nope. If the business logic wants to &quot;schedule&quot; jobs,<br>
            &gt;                 to send messages, it can do it.<br>
            &gt;                 But not inside of the admin UI.  See also:<br>
            &gt;                 <a href="http://staging.aerogear.org/docs/specs/aerogear-server-push/" target="_blank">http://staging.aerogear.org/docs/specs/aerogear-server-push/</a><br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;                         Corinne<br>
            &gt;<br>
            &gt;<br>
            &gt;                         On Thursday, May 23, 2013, Hylke Bons wrote:<br>
            &gt;                                 Yes, that&#39;s great!<br>
            &gt;                                 Thanks,<br>
            &gt;<br>
            &gt;                                 Hylke<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;                                 On 23/05/2013 15:08, Matthias<br>
            &gt;                                 Wessendorf wrote:<br>
            &gt;<br>
            &gt;                                 &gt; Hylke,<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt; here is a &quot;spec&quot;, which has<br>
            &gt;                                 &gt; use-cases, scenarios of the Server<br>
            &gt;                                 &gt; Usage:<br>
            &gt;                                 &gt; <a href="http://staging.aerogear.org/docs/specs/aerogear-server-push/" target="_blank">http://staging.aerogear.org/docs/specs/aerogear-server-push/</a><br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt; Let me know if that is good enough<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt; On Thu, May 23, 2013 at 3:02 PM,<br>
            &gt;                                 &gt; Hylke Bons &lt;<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>&gt; wrote:<br>
            &gt;                                 &gt;         Hi,<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;         I don&#39;t feel confident<br>
            &gt;                                 &gt;         enough to comment on these<br>
            &gt;                                 &gt;         right now as I&#39;m currently<br>
            &gt;                                 &gt;         trying to learn more about<br>
            &gt;                                 &gt;         how AeroGear and push<br>
            &gt;                                 &gt;         notifications work, but<br>
            &gt;                                 &gt;         hopefully I wil be able to<br>
            &gt;                                 &gt;         soon. :)<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;         What are the<br>
            &gt;                                 &gt;         requirements/functionalities<br>
            &gt;                                 &gt;         that you&#39;ve based this work<br>
            &gt;                                 &gt;         on? A few usecases might be<br>
            &gt;                                 &gt;         helpful too, so we can have<br>
            &gt;                                 &gt;         a better view on what you&#39;re<br>
            &gt;                                 &gt;         trying to design here.<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;         Thanks,<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;         Hylke<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;         On 23/05/2013 13:54, Lucas<br>
            &gt;                                 &gt;         Holmquist wrote:<br>
            &gt;                                 &gt;<br>
            &gt;                                 &gt;         &gt; they look pretty good.<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt; i&#39;m sure once we start<br>
            &gt;                                 &gt;         &gt; implementing it, there<br>
            &gt;                                 &gt;         &gt; will be tweaks.<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt; not sure if this is<br>
            &gt;                                 &gt;         &gt; important at this point,<br>
            &gt;                                 &gt;         &gt;  but will this Admin UI<br>
            &gt;                                 &gt;         &gt; also receive<br>
            &gt;                                 &gt;         &gt; notifications, like when<br>
            &gt;                                 &gt;         &gt; someone starts the<br>
            &gt;                                 &gt;         &gt; installed app for the<br>
            &gt;                                 &gt;         &gt; first time and registers<br>
            &gt;                                 &gt;         &gt; their device token?<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt; On May 23, 2013, at 8:43<br>
            &gt;                                 &gt;         &gt; AM, Matthias Wessendorf<br>
            &gt;                                 &gt;         &gt; &lt;<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>&gt; wrote:<br>
            &gt;                                 &gt;         &gt;<br>
            &gt;                                 &gt;         &gt; &gt; Hello,<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt; a few weeks ago, I<br>
            &gt;                                 &gt;         &gt; &gt; started to create a<br>
            &gt;                                 &gt;         &gt; &gt; (clickable) MockUp for<br>
            &gt;                                 &gt;         &gt; &gt; our Admin UI.<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt; <a href="https://issues.jboss.org/browse/AEROGEAR-1170" target="_blank">https://issues.jboss.org/browse/AEROGEAR-1170</a><br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt; It is (currently) based<br>
            &gt;                                 &gt;         &gt; &gt; on Bootstrap, because of<br>
            &gt;                                 &gt;         &gt; &gt; my &#39;awesome&#39; CSS/Design<br>
            &gt;                                 &gt;         &gt; &gt; skillz.<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt; However, the cover the<br>
            &gt;                                 &gt;         &gt; &gt; functionality.<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt; Any thoughts about<br>
            &gt;                                 &gt;         &gt; &gt; these? I am also<br>
            &gt;                                 &gt;         &gt; &gt; interested in moving<br>
            &gt;                                 &gt;         &gt; &gt; them forward, to that we<br>
            &gt;                                 &gt;         &gt; &gt; can give the PushEE<br>
            &gt;                                 &gt;         &gt; &gt; server an UI :)<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt; Thanks,<br>
            &gt;                                 &gt;         &gt; &gt; Matthias<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt; --<br>
            &gt;                                 &gt;         &gt; &gt; Matthias Wessendorf<br>
            &gt;                                 &gt;         &gt; &gt;<br>
            &gt;                                 &gt;         &gt; &gt; blog:<br>
            &gt;                                 &gt;         &gt; &gt; <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
            &gt;                                 &gt;         &gt; &gt; sessions:<br>
            &gt;                                 &gt;         &gt; &gt; <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
            &gt;                                 &gt;         &gt; &gt; twitter:<br>
            &gt;<br>
            &gt;<br>
            &gt;                         _______________________________________________<br>
            &gt;                         aerogear-dev mailing list<br>
            &gt;                         <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
            &gt;                         <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;                 --<br>
            &gt;                 Matthias Wessendorf<br>
            &gt;<br>
            &gt;                 blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
            &gt;                 sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
            &gt;<br>
            &gt;                 twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
            &gt;<br>
            &gt;                 _______________________________________________<br>
            &gt;                 aerogear-dev mailing list<br>
            &gt;                 <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
            &gt;                 <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;         _______________________________________________<br>
            &gt;         aerogear-dev mailing list<br>
            &gt;         <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
            &gt;         <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt; --<br>
            &gt; Matthias Wessendorf<br>
            &gt;<br>
            &gt; blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
            &gt; sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
            &gt; twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
            &gt; _______________________________________________<br>
            &gt; aerogear-dev mailing list<br>
            &gt; <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
            &gt; <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
            <br>
            <br>
            _______________________________________________<br>
            aerogear-dev mailing list<br>
            <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
            <br>
        </blockquote>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        <br>
        <br>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <blockquote>
        -- <br>
        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>
    </blockquote>
</blockquote>
<blockquote type="CITE">
    <br>
    <br>
</blockquote>
<blockquote type="CITE">
    <br>
    <br>
</blockquote>
<blockquote type="CITE">
    -- <br>
    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>
</blockquote>
<blockquote type="CITE">
<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></div>

<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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><br clear="all"><div><br></div>-- <br>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></div>