The WebPush Server needs updates too, to be compliant to latest version of
the spec, right?
Right, but I consider it as a necessary step, which have to be done before
summer :)
Another possible scenario: complete work on integration with Chrome and
Firefox before GSoC and work on WebPush Server updates and integration with
UPS during the whole summer.
Which task has a higher priority for AeroGear?
Best regards,
Idel Pivnitskiy
--
E-mail: idel.pivnitskiy(a)gmail.com
Twitter: @idelpivnitskiy <
https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <
https://github.com/idelpivnitskiy>
On Mon, Mar 21, 2016 at 11:27 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
a few more questions
On Mon, Mar 21, 2016 at 9:21 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
> Hi Idel,
>
> 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?
>
> On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <
> idel.pivnitskiy(a)gmail.com> wrote:
>
>> Hello community!
>>
>> 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.
>>
>> I'm highly motivated to continue my work on WebPush protocol and move it
>> to UPS!
>>
>> Expected results for GSoC 2016 project:
>>
>> - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>> browsers into UPS.
>> - Integrate AeroGear WebPush server with UnifiedPush Server.
>> - Good test coverage for the new code.
>> - Documentation for all new developments and changes.
>> - Demo application for showing the work of WebPush protocol in
>> action with UPS!
>>
>> I think we could have two demos :)
- pure WebPush, via UPS, to a browser/device
- GCM push, received on WebPush APIs, going through UPS
>
>> -
>>
>>
>> Possible additional tasks which could be done:
>>
>> - Java client for AppServer (similar as a current client for User
>> Agents).
>> - Rewrite java clients with native Java 9 HTTP/2 API.
>>
>> what clients do you mean ?
>
>> -
>> - Port webpush-codec directly to Netty. It will simplify WebPush
>> Server code base and attract other developers to improve the core of the
>> protocol.
>>
>> Glad to see your feedback!
>>
>> Best regards,
>> Idel Pivnitskiy
>> --
>> Twitter: @idelpivnitskiy <
https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <
https://github.com/idelpivnitskiy>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> sessions:
http://www.slideshare.net/mwessendorf
> twitter:
http://twitter.com/mwessendorf
>
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev