<div dir="ltr"><div>I understand the implications,</div><div><br></div>but are you worried about storing messages per se or rather fact that UPS would need to store anything?<div><br></div><div>Storing messages is required part in case of SimplePush deployment - all other networks can be approached as fire&forget.</div><div><br></div><div>While up to the point you start to use SImplePush you are free of managing custom storage and exposing your storage endpoint to the client, at that point you simply have to -> ouch, that hurts.</div><div><br></div><div>---</div><div><br></div><div>In case this does not get into UPS, I would suggest at least having interceptor on UPS side that would enable extension developers to plug such a storage (we are limited by a fact that Push Sender does not know an endpoint URL, actually it does not have any connection to Sender at all, so there are limited options to connect those two).</div><div><br></div><div>Or maybe he can even do that today with JAX-RS interceptors? :-)</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 20, 2014 at 3:46 PM, Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@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 style="word-wrap:break-word"><br><div><span class=""><blockquote type="cite"><div>On Oct 20, 2014, at 9:44 AM, Lukáš Fryč <<a href="mailto:lukas.fryc@gmail.com" target="_blank">lukas.fryc@gmail.com</a>> wrote:</div><br><div><div dir="ltr">Clarification: this was meant as UnifiedPushClient extension, rather then SimplePush's one (bad wording)</div></div></blockquote><div><br></div></span><div>i think i might still be a no, because of storing messages</div><div><div class="h5"><br><blockquote type="cite"><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 20, 2014 at 3:25 PM, Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@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 style="word-wrap:break-word">I vote no for this.<div><br></div><div>I think storing messages, for any period of time is bad.</div><div><br></div><div>I think SimplePush should stay “Simple” and we should follow the spec on this. </div><div><div><div><br><div><blockquote type="cite"><div>On Oct 20, 2014, at 8:59 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>> wrote:</div><br><div><div dir="ltr">I'm just worried about storing the message, for stuff like privacy, for instance. Let's make a really short TTL or better let's delete the mesage right after it has been retrieved.<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 20, 2014 at 2:51 PM, Lukáš Fryč <span dir="ltr"><<a href="mailto:lukas.fryc@gmail.com" target="_blank">lukas.fryc@gmail.com</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"><div>Awesome, great to hear that SimplePush will get a native support for a full message content.</div><div><br></div><div>As Erik said, in the meantime, we could unify this behavior.</div>I have created the associated issue: <a href="https://issues.jboss.org/browse/AGPUSH-1073" target="_blank">https://issues.jboss.org/browse/AGPUSH-1073</a><div><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 20, 2014 at 2:07 PM, Erik Jan de Wit <span dir="ltr"><<a href="mailto:edewit@redhat.com" target="_blank">edewit@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 style="word-wrap:break-word">Hi Luká<font face="Helvetica Neue, Helvetica, Arial, san-serif"><span style="line-height:16px">š,</span></font><div><font face="Helvetica Neue, Helvetica, Arial, san-serif"><span style="line-height:16px"><br></span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, san-serif"><span style="line-height:16px">I like that idea, because in the end our goal is to unify. And I think that the simple push protocol will be changed in the future to allow for ‘normal’ message sending. So we could fallback afterwards.</span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, san-serif"><span style="line-height:16px"><br></span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, san-serif"><span style="line-height:16px">Cheers,</span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, san-serif"><span style="line-height:16px"><span style="white-space:pre-wrap"> </span>Erik Jan</span></font></div><div><font face="Helvetica Neue, Helvetica, Arial, san-serif"><span style="line-height:16px"><br></span></font><div><div><div><div>On 20 Oct,2014, at 13:58 , Lukáš Fryč <<a href="mailto:lukas.fryc@gmail.com" target="_blank">lukas.fryc@gmail.com</a>> wrote:</div><br></div></div><blockquote type="cite"><div><div><div dir="ltr">Hey guys,<div><br></div><div>I'm working on a demo of UPS pushing to iOS, Android, Windows, as well as Firefox OS using our Cordova plugin.</div><div><br></div><div>But as you know, with FFOS it is not that simple - since SimplePush protocol allows to transfer just incremental versions, we are not able to deliver any interesting message.</div><div><br></div><div>UnifiedPush Server could be a correct place where we unify and shield our users from this limitation:</div><div><br></div><div><br></div><div>my idea is storing the message on UPS under the SimplePush endpoint URL. Once the message with version reaches the client, he would contact UPS to retrieve this message under a key ( pushEndpoint, version ).</div><div><br></div><div>The messages could have default built-in TTL to allow periodic cleanup.</div><div><br></div><div>What do you think?</div><div><br></div><div><br></div><div>Cheers,</div><div><br></div><div>~ Lukas</div></div></div></div>
_______________________________________________<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></blockquote></div><br></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></div></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></div>
_______________________________________________<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></div></blockquote></div><br></div></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></div>
_______________________________________________<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></div></blockquote></div></div></div><br></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>