<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 28, 2013 at 3:55 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Tue, May 28, 2013 at 3:42 PM, Apostolos Emmanouilidis <span dir="ltr"><<a href="mailto:aemmanou@redhat.com" target="_blank">aemmanou@redhat.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">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.<br></blockquote><div><br></div><div><br></div></div><div>I agree, since I am also not a fan of sending messages from the UI. However folks keep asking, </div><div>so I asked for that JIRA. this will, for sure, not be included in the first release;</div>
<div class="im">
<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">
<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."<br></blockquote><div><br></div></div><div>Not needed.</div><div><br></div><div>We have a ticket that we need a "scheduled" job to receive invalid from the network(s), in order to perform the "tidy-up":</div>
<div><a href="https://issues.jboss.org/browse/AGPUSH-45" target="_blank">https://issues.jboss.org/browse/AGPUSH-45</a><br></div><div><br></div><div><br></div><div>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".</div>
<div><br></div><div>No need to stick this "request feedback" into the UI</div></div></div></div></blockquote><div><br></div><div style>Besides a simple field to schedule the actual "interval" :)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5"><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">
<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.<br>
<div><div><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" target="_blank">corinnekrych@gmail.com</a>> wrote:<br>
> <a href="https://issues.jboss.org/browse/AGPUSH-38" target="_blank">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" target="_blank">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" target="_blank">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/" target="_blank">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/" target="_blank">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" target="_blank">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" target="_blank">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" target="_blank">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/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
> > > > sessions:<br>
> > > > <a href="http://www.slideshare.net/mwessendorf" target="_blank">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" 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>
><br>
><br>
><br>
><br>
> --<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>
><br>
> twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><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>
><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>
><br>
><br>
><br>
> --<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><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>
<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>
</div></div></blockquote></div></div></div><div><div class="h5"><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></div></div>
</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>