<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 21, 2016 at 11:55 AM, Idel Pivnitskiy <span dir="ltr"><<a href="mailto:idel.pivnitskiy@gmail.com" target="_blank">idel.pivnitskiy@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"><span class=""><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"><span style="font-size:12.8px">The WebPush Server needs updates too, to be compliant to latest version of the spec, right?</span></blockquote><div><br></div></span><div>Right, but I consider it as a necessary step, which have to be done before summer :)</div><div><br></div><div>Another possible scenario: complete work on integration with Chrome and Firefox before GSoC </div></div></blockquote><div><br></div><div>work like that is always more than welcome - and would be handy to actually show the 'standalone' solution: pure WebPush -> FF/Chrome (without UPS).</div><div>I think we could a screencast on this one, once done</div><div><br></div><div>-M</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>and work on WebPush Server updates and integration with UPS during the whole summer.</div><div><br></div><div>Which task has a higher priority for AeroGear?</div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Best regards,<div>Idel Pivnitskiy</div><div>--<br><div>E-mail: <a href="mailto:idel.pivnitskiy@gmail.com" target="_blank">idel.pivnitskiy@gmail.com</a></div></div><div>Twitter: <a href="https://twitter.com/idelpivnitskiy" target="_blank">@idelpivnitskiy</a></div><div>GitHub: <a href="https://github.com/idelpivnitskiy" target="_blank">@idelpivnitskiy</a></div></div></div></div></div></div></div></div></div></div><div><div class="h5">
<br><div class="gmail_quote">On Mon, Mar 21, 2016 at 11:27 AM, 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">a few more questions<div class="gmail_extra"><br><div class="gmail_quote"><span>On Mon, Mar 21, 2016 at 9:21 AM, 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">Hi Idel,<div><br></div><div>these ideas sound extremely awesome, and I agree they are a logic next steps on the ground work of your project last year. The WebPush Server needs updates too, to be compliant to latest version of the spec, right?</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <span dir="ltr"><<a href="mailto:idel.pivnitskiy@gmail.com" target="_blank">idel.pivnitskiy@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div>Hello community!</div><div><br></div><div>I'm happy to work with you during the last year! Thank you for the great project! I use it for the pleasured Open Source development when I have free time and I use UPS with my own projects at work.</div><div><br></div><div>I'm highly motivated to continue my work on WebPush protocol and move it to UPS!</div><div><br></div><div><div>Expected results for GSoC 2016 project:</div><div><ul><li>Add WebPush support for Google Chrome, Mozilla Firefox and Safari browsers into UPS.<br></li><li>Integrate AeroGear WebPush server with UnifiedPush Server.<br></li><li>Good test coverage for the new code.<br></li><li>Documentation for all new developments and changes.<br></li><li>Demo application for showing the work of WebPush protocol in action with UPS!<br></li></ul></div></div></div></div></div></blockquote></div></div></blockquote></span><div>I think we could have two demos :)</div><div><br></div><div>- pure WebPush, via UPS, to a browser/device</div><div>- GCM push, received on WebPush APIs, going through UPS</div><span><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><ul><li></li></ul></div><div><br></div><div>Possible additional tasks which could be done:</div><div><ul><li>Java client for AppServer (similar as a current client for User Agents).<br></li><li>Rewrite java clients with native Java 9 HTTP/2 API.<br></li></ul></div></div></div></div></div></blockquote></div></div></blockquote></span><div>what clients do you mean ? </div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><ul><li></li><li>Port webpush-codec directly to Netty. It will simplify WebPush Server code base and attract other developers to improve the core of the protocol.</li></ul></div></div><div>Glad to see your feedback!</div><br clear="all"><div><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Best regards,<div>Idel Pivnitskiy</div><div>--<br></div><div>Twitter: <a href="https://twitter.com/idelpivnitskiy" target="_blank">@idelpivnitskiy</a></div><div>GitHub: <a href="https://github.com/idelpivnitskiy" target="_blank">@idelpivnitskiy</a></div></div></div></div></div></div></div>
</div>
<br></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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><span><font color="#888888"><br></font></span></blockquote></div><span><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>
</blockquote></span></div><span><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>
</span></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" rel="noreferrer" 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">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><br clear="all"><div><br></div>-- <br><div class="gmail_signature">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>