<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.4">
</HEAD>
<BODY>
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 "tidy-up" procedure is executed. <BR>
<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 <<A HREF="mailto:matzew@apache.org">matzew@apache.org</A>> 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 <<A HREF="mailto:aemmanou@redhat.com">aemmanou@redhat.com</A>> 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 "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."
</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 "scheduled" job to receive invalid from the network(s), in order to perform the "tidy-up":
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<A HREF="https://issues.jboss.org/browse/AGPUSH-45">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 "tidy-up".
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
No need to stick this "request feedback" into the UI
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
Besides a simple field to schedule the actual "interval" :)
</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 "inactive" tokens should be removed<BR>
or marked as "token to be deleted" 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>
> perfect, thanks!<BR>
><BR>
><BR>
> On Fri, May 24, 2013 at 9:54 AM, Corinne Krych<BR>
> <<A HREF="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</A>> wrote:<BR>
> <A HREF="https://issues.jboss.org/browse/AGPUSH-38">https://issues.jboss.org/browse/AGPUSH-38</A><BR>
><BR>
><BR>
> for this (optional) 1.2.0 feature<BR>
><BR>
><BR>
><BR>
><BR>
> On 24 May 2013 08:01, Matthias Wessendorf <<A HREF="mailto:matzew@apache.org">matzew@apache.org</A>><BR>
> wrote:<BR>
><BR>
><BR>
><BR>
> On Fri, May 24, 2013 at 12:12 AM, Corinne Krych<BR>
> <<A HREF="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</A>> wrote:<BR>
> Will the adminui provides UI to send<BR>
> notification message?<BR>
> It could be useful for testing purpose.<BR>
><BR>
><BR>
> Not sure, if we do it for August, but can u file a<BR>
> JIRA ?<BR>
><BR>
><BR>
><BR>
> Or another use case could be to send automatic<BR>
> - rule triggerred - messages.<BR>
><BR>
><BR>
><BR>
><BR>
> Nope. If the business logic wants to "schedule" jobs,<BR>
> to send messages, it can do it.<BR>
> But not inside of the admin UI. See also:<BR>
> <A HREF="http://staging.aerogear.org/docs/specs/aerogear-server-push/">http://staging.aerogear.org/docs/specs/aerogear-server-push/</A><BR>
><BR>
><BR>
><BR>
><BR>
> Corinne<BR>
><BR>
><BR>
> On Thursday, May 23, 2013, Hylke Bons wrote:<BR>
> Yes, that's great!<BR>
> Thanks,<BR>
><BR>
> Hylke<BR>
><BR>
><BR>
><BR>
> On 23/05/2013 15:08, Matthias<BR>
> Wessendorf wrote:<BR>
><BR>
> > Hylke,<BR>
> ><BR>
> ><BR>
> > here is a "spec", which has<BR>
> > use-cases, scenarios of the Server<BR>
> > Usage:<BR>
> > <A HREF="http://staging.aerogear.org/docs/specs/aerogear-server-push/">http://staging.aerogear.org/docs/specs/aerogear-server-push/</A><BR>
> ><BR>
> ><BR>
> ><BR>
> ><BR>
> ><BR>
> > Let me know if that is good enough<BR>
> ><BR>
> ><BR>
> > On Thu, May 23, 2013 at 3:02 PM,<BR>
> > Hylke Bons <<A HREF="mailto:hbons@redhat.com">hbons@redhat.com</A>> wrote:<BR>
> > Hi,<BR>
> ><BR>
> > I don't feel confident<BR>
> > enough to comment on these<BR>
> > right now as I'm currently<BR>
> > trying to learn more about<BR>
> > how AeroGear and push<BR>
> > notifications work, but<BR>
> > hopefully I wil be able to<BR>
> > soon. :)<BR>
> ><BR>
> > What are the<BR>
> > requirements/functionalities<BR>
> > that you've based this work<BR>
> > on? A few usecases might be<BR>
> > helpful too, so we can have<BR>
> > a better view on what you're<BR>
> > trying to design here.<BR>
> ><BR>
> > Thanks,<BR>
> ><BR>
> > Hylke<BR>
> ><BR>
> ><BR>
> ><BR>
> > On 23/05/2013 13:54, Lucas<BR>
> > Holmquist wrote:<BR>
> ><BR>
> > > they look pretty good.<BR>
> > ><BR>
> > ><BR>
> > > i'm sure once we start<BR>
> > > implementing it, there<BR>
> > > will be tweaks.<BR>
> > ><BR>
> > ><BR>
> > ><BR>
> > ><BR>
> > > not sure if this is<BR>
> > > important at this point,<BR>
> > > but will this Admin UI<BR>
> > > also receive<BR>
> > > notifications, like when<BR>
> > > someone starts the<BR>
> > > installed app for the<BR>
> > > first time and registers<BR>
> > > their device token?<BR>
> > ><BR>
> > ><BR>
> > ><BR>
> > ><BR>
> > ><BR>
> > > On May 23, 2013, at 8:43<BR>
> > > AM, Matthias Wessendorf<BR>
> > > <<A HREF="mailto:matzew@apache.org">matzew@apache.org</A>> wrote:<BR>
> > ><BR>
> > > > Hello,<BR>
> > > ><BR>
> > > ><BR>
> > > > a few weeks ago, I<BR>
> > > > started to create a<BR>
> > > > (clickable) MockUp for<BR>
> > > > our Admin UI.<BR>
> > > ><BR>
> > > ><BR>
> > > > <A HREF="https://issues.jboss.org/browse/AEROGEAR-1170">https://issues.jboss.org/browse/AEROGEAR-1170</A><BR>
> > > ><BR>
> > > ><BR>
> > > > It is (currently) based<BR>
> > > > on Bootstrap, because of<BR>
> > > > my 'awesome' CSS/Design<BR>
> > > > skillz.<BR>
> > > ><BR>
> > > ><BR>
> > > ><BR>
> > > > However, the cover the<BR>
> > > > functionality.<BR>
> > > ><BR>
> > > ><BR>
> > > > Any thoughts about<BR>
> > > > these? I am also<BR>
> > > > interested in moving<BR>
> > > > them forward, to that we<BR>
> > > > can give the PushEE<BR>
> > > > server an UI :)<BR>
> > > ><BR>
> > > ><BR>
> > > > Thanks,<BR>
> > > > Matthias<BR>
> > > ><BR>
> > > ><BR>
> > > > --<BR>
> > > > Matthias Wessendorf<BR>
> > > ><BR>
> > > > blog:<BR>
> > > > <A HREF="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</A><BR>
> > > > sessions:<BR>
> > > > <A HREF="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</A><BR>
> > > > twitter:<BR>
><BR>
><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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</A><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
> --<BR>
> Matthias Wessendorf<BR>
><BR>
> blog: <A HREF="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</A><BR>
> sessions: <A HREF="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</A><BR>
><BR>
> twitter: <A HREF="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</A><BR>
><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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</A><BR>
><BR>
><BR>
><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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</A><BR>
><BR>
><BR>
><BR>
><BR>
> --<BR>
> Matthias Wessendorf<BR>
><BR>
> blog: <A HREF="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</A><BR>
> sessions: <A HREF="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</A><BR>
> twitter: <A HREF="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</A><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">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">aerogear-dev@lists.jboss.org</A><BR>
<A HREF="https://lists.jboss.org/mailman/listinfo/aerogear-dev">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/">http://matthiaswessendorf.wordpress.com/</A><BR>
sessions: <A HREF="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</A><BR>
twitter: <A HREF="http://twitter.com/mwessendorf">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/">http://matthiaswessendorf.wordpress.com/</A><BR>
sessions: <A HREF="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</A><BR>
twitter: <A HREF="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</A>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
_______________________________________________
aerogear-dev mailing list
<A HREF="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</A>
<A HREF="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</A>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>