<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 2, 2015 at 10:02 PM, delalis <span dir="ltr"><<a href="mailto:delalis@gmail.com" target="_blank">delalis@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Im wondering if this is a case of "were doing it wrong" and we should find a<br>
new place for the UPS to live that can be contacted directly by the devices<br>
with the push-config json info pointing right to it....<br></blockquote><div>Well you have maybe a valid use case/architecture choice to not want to expose UPS but indeed if it can be exposed you can avoid some hacky stuff I suggested in my previous emails ;) </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11738.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11738.html</a><br>
<div class="HOEnZb"><div class="h5">Sent from the aerogear-dev mailing list archive at Nabble.com.<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>
</div></div></blockquote></div><br></div></div>