Thanks Matthias

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.

On Tue, 2013-05-28 at 16:02 +0200, Matthias Wessendorf wrote:

On Tue, May 28, 2013 at 3:55 PM, Matthias Wessendorf <matzew@apache.org> wrote:

On Tue, May 28, 2013 at 3:42 PM, Apostolos Emmanouilidis <aemmanou@redhat.com> wrote:

In my opinion, adding a UI to send notification message will make the
Admin UI quite complex. If the users are able to send notification
messages from the UI they should also be able to receive the feedback
information from the Push Notification servers.

I agree, since I am also not a fan of sending messages from the UI. However folks keep asking,

so I asked for that JIRA. this will, for sure, not be included in the first release;

For example Apple mentions that "APNs has a feedback service that
maintains a per-application list of devices for which there were
failed-delivery attempts (that is, APNs was unable to deliver a push
notification to an application on a device). Periodically, the provider
should connect with the feedback service to see what devices have
persistent failures so that it can refrain from sending push
notifications to them."

Not needed.

We have a ticket that we need a "scheduled" job to receive invalid from the network(s), in order to perform the "tidy-up":

https://issues.jboss.org/browse/AGPUSH-45

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".

No need to stick this "request feedback" into the UI

Besides a simple field to schedule the actual "interval" :)

This means that extra functionality will be required, like the
synchronization of the tokens. The "inactive" tokens should be removed
or marked as "token to be deleted" and let the admin user decide whether
they will be deleted or not.

On Fri, 2013-05-24 at 10:18 +0200, Matthias Wessendorf wrote:
> perfect, thanks!
>
>
> On Fri, May 24, 2013 at 9:54 AM, Corinne Krych
> <corinnekrych@gmail.com> wrote:
> https://issues.jboss.org/browse/AGPUSH-38
>
>
> for this (optional) 1.2.0 feature
>
>
>
>
> On 24 May 2013 08:01, Matthias Wessendorf <matzew@apache.org>
> wrote:
>
>
>
> On Fri, May 24, 2013 at 12:12 AM, Corinne Krych
> <corinnekrych@gmail.com> wrote:
> Will the adminui provides UI to send
> notification message?
> It could be useful for testing purpose.
>
>
> Not sure, if we do it for August, but can u file a
> JIRA ?
>
>
>
> Or another use case could be to send automatic
> - rule triggerred - messages.
>
>
>
>
> Nope. If the business logic wants to "schedule" jobs,
> to send messages, it can do it.
> But not inside of the admin UI. See also:
> http://staging.aerogear.org/docs/specs/aerogear-server-push/
>
>
>
>
> Corinne
>
>
> On Thursday, May 23, 2013, Hylke Bons wrote:
> Yes, that's great!
> Thanks,
>
> Hylke
>
>
>
> On 23/05/2013 15:08, Matthias
> Wessendorf wrote:
>
> > Hylke,
> >
> >
> > here is a "spec", which has
> > use-cases, scenarios of the Server
> > Usage:
> > http://staging.aerogear.org/docs/specs/aerogear-server-push/
> >
> >
> >
> >
> >
> > Let me know if that is good enough
> >
> >
> > On Thu, May 23, 2013 at 3:02 PM,
> > Hylke Bons <hbons@redhat.com> wrote:
> > Hi,
> >
> > I don't feel confident
> > enough to comment on these
> > right now as I'm currently
> > trying to learn more about
> > how AeroGear and push
> > notifications work, but
> > hopefully I wil be able to
> > soon. :)
> >
> > What are the
> > requirements/functionalities
> > that you've based this work
> > on? A few usecases might be
> > helpful too, so we can have
> > a better view on what you're
> > trying to design here.
> >
> > Thanks,
> >
> > Hylke
> >
> >
> >
> > On 23/05/2013 13:54, Lucas
> > Holmquist wrote:
> >
> > > they look pretty good.
> > >
> > >
> > > i'm sure once we start
> > > implementing it, there
> > > will be tweaks.
> > >
> > >
> > >
> > >
> > > not sure if this is
> > > important at this point,
> > > but will this Admin UI
> > > also receive
> > > notifications, like when
> > > someone starts the
> > > installed app for the
> > > first time and registers
> > > their device token?
> > >
> > >
> > >
> > >
> > >
> > > On May 23, 2013, at 8:43
> > > AM, Matthias Wessendorf
> > > <matzew@apache.org> wrote:
> > >
> > > > Hello,
> > > >
> > > >
> > > > a few weeks ago, I
> > > > started to create a
> > > > (clickable) MockUp for
> > > > our Admin UI.
> > > >
> > > >
> > > > https://issues.jboss.org/browse/AEROGEAR-1170
> > > >
> > > >
> > > > It is (currently) based
> > > > on Bootstrap, because of
> > > > my 'awesome' CSS/Design
> > > > skillz.
> > > >
> > > >
> > > >
> > > > However, the cover the
> > > > functionality.
> > > >
> > > >
> > > > Any thoughts about
> > > > these? I am also
> > > > interested in moving
> > > > them forward, to that we
> > > > can give the PushEE
> > > > server an UI :)
> > > >
> > > >
> > > > Thanks,
> > > > Matthias
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog:
> > > > http://matthiaswessendorf.wordpress.com/
> > > > sessions:
> > > > http://www.slideshare.net/mwessendorf
> > > > twitter:
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
>
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev