<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 24, 2015 at 1:45 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><div class="gmail_quote"><span class="">On Mon, Aug 24, 2015 at 7:22 PM, Luke 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 dir="ltr">so i decided to take a gander at the push client lib in the aerogear.js project. Currently if someone would like to use it, they have a couple options.<div><br></div><div>1. download the whole lib,</div><div>2. download a custom build from the website</div><div>3. download a custom build from bower</div><div>4. create a custom build from source</div><div><br></div><div>In the past i think i was against breaking out pieces of the JS lib into separate repo's since we could just use the AeroGearComponents repo i created for custom builds. But i think with the state of the JS lib(not sure where it's going), it might make sense to, at least with the push lib(perhaps the simplePush polyfill also) to break those out into separate repo's similar to the other client projects.</div><div><br></div><div>I think the starting vision of the project has changed, so perhaps this change is good.(this should probably be a whole separate thread)</div><div><br></div><div>Now that Chrome and Safari have push in the browser, FF is getting it also very soon, it's possible this part of the library will be used more</div><div><br></div><div><br></div><div>thoughts?</div></div></blockquote><div><br></div></span><div>yeah, makes sense to separate it.</div><div>And while getting back at the JS push lib, due to more interest in browser based push, I think it would be good to revisit the security aspects, for device (installation) registration against UPS. </div></div></div></div></blockquote><div>yea, this is an issue. Not sure the best way to approach this though. but thats a different conversation i think </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><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><font color="#888888"><div><br></div><div>-Luke </div></font></span></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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>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>
</font></span></div></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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div></div>