Hi Idel,
it is editable :-)
On Wed, Apr 1, 2015 at 2:24 PM, Idel Pivnitskiy <idel.pivnitskiy(a)gmail.com>
wrote:
I'm ready to update my proposal! Here is what I want to add:
https://www.dropbox.com/s/y51denpp3b4ojar/Idel.Pivnitskiy.WebPush.pdf
Please, leave comments if you have suggestions of how improve it.
Also, please, enable edit mode for my proposal on Melange:
https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc20...
Best regards,
Idel Pivnitskiy
--
E-mail: Idel.Pivnitskiy(a)gmail.com
GitHub: @idelpivnitskiy <
https://github.com/idelpivnitskiy>
2015-03-31 16:20 GMT+03:00 Sebastien Blanc <scm.blanc(a)gmail.com>:
> +1
>
> On Tue, Mar 31, 2015 at 3:20 PM, Matthias Wessendorf <matzew(a)apache.org>
> wrote:
>
>> That's a good point. I thought I added it :-) But yeah, keeping our own
>> server to stay up-to-date with this emerging spec is good for all of us :-)
>>
>> On Tue, Mar 31, 2015 at 3:15 PM, Idel Pivnitskiy <
>> idel.pivnitskiy(a)gmail.com> wrote:
>>
>>> If vert.x server has a low priority and may take a long time I can
>>> remove it from my proposal and add another task:
>>> "Update WebPush Server to use a new WebPush Protocol spec".
Because
>>> current spec will expire during this summer (June 15, 2015).
>>>
http://tools.ietf.org/html/draft-thomson-webpush-http2-02
>>>
>>> Best regards,
>>> Idel Pivnitskiy
>>> --
>>> E-mail: Idel.Pivnitskiy(a)gmail.com
>>> GitHub: @idelpivnitskiy <
https://github.com/idelpivnitskiy>
>>>
>>> 2015-03-31 15:54 GMT+03:00 Matthias Wessendorf <matzew(a)apache.org>:
>>>
>>>>
>>>>
>>>> On Tue, Mar 31, 2015 at 2:48 PM, Sebastien Blanc
<scm.blanc(a)gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Tue, Mar 31, 2015 at 12:48 PM, Matthias Wessendorf <
>>>>> matzew(a)apache.org> wrote:
>>>>>
>>>>>> Hi Idel,
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Mar 31, 2015 at 12:14 PM, Idel Pivnitskiy <
>>>>>> idel.pivnitskiy(a)gmail.com> wrote:
>>>>>>
>>>>>>> Thanks to all!
>>>>>>>
>>>>>>> Sounds interesting! I've read source code of UPS and
SimplePush and
>>>>>>> it won't be a problem for me to add support for WebPush
>>>>>>>
>>>>>>
>>>>>> sweet
>>>>>>
>>>>>> and update aerogear-unifiedpush-java-client to support it too.
>>>>>>>
>>>>>>
>>>>>> that one does likely does not need any update. It sends the
payload
>>>>>> to UPS, and UPS delivers to all supported Push Networks (e.g APNs
or a
>>>>>> WebPush enabled server)
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Also I can write something like
aerogear-simplepush-java-client for
>>>>>>> WebPush and some vert.x module.
>>>>>>> Do I understand this part of the job?
>>>>>>>
>>>>>> That's right. Get a client codec for WebPush in place, stick
that
>>>>>> into a client like the above for simplepush. Leverage that client
in a
>>>>>> vert.x 3 module
>>>>>>
>>>>> For vert.x, what I had in mind was more an implementation of the
>>>>> server (like Dan did for SimplePush) but that makes it maybe a bit
too much
>>>>> ...
>>>>>
>>>>
>>>> if time allows that - ok, but I don't see too much value of creating
a
>>>> server that directly is competing with our own server....
>>>>
>>>>
>>>>>
>>>>>>
>>>>>>>
>>>>>>> But I'm not familiar with IoT devices. Where I can find
how to
>>>>>>> deploy test applications and test them? Could you, please,
clarify this
>>>>>>> idea?
>>>>>>>
>>>>>>
>>>>>> Some highlevel ideas:
>>>>>>
>>>>>>
https://matthiaswessendorf.wordpress.com/2015/03/25/push-notifications-an...
>>>>>>
>>>>>> Checkout Sebi's cool videos. IMO if something runs on a Pi,
Ardino
>>>>>> or a Lego Robot :-) we are talking. hehe
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Idel Pivnitskiy
>>>>>>> --
>>>>>>> E-mail: Idel.Pivnitskiy(a)gmail.com
>>>>>>> GitHub: @idelpivnitskiy
<
https://github.com/idelpivnitskiy>
>>>>>>>
>>>>>>> 2015-03-30 17:03 GMT+03:00 Matthias Wessendorf
<matzew(a)apache.org>:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> all of these items could be all done in one GSOC project.
Perhaps,
>>>>>>>> to have something more "fancy", the project
aims to offer "WebPush support
>>>>>>>> for mobile cloud services on IoT devices".
>>>>>>>> Needed deliverables:
>>>>>>>> * UPS support for WebPush
>>>>>>>> * Java client of the WebPush wireprotocol, that can be
wrapped in
>>>>>>>> the mentioned vert.x module
>>>>>>>> * demo app of showing the WebPush standard on IoT
devices, with
>>>>>>>> mobile cloud services (like UPS)
>>>>>>>>
>>>>>>>> IMO this would make a nice project. It even may be also
the case
>>>>>>>> that some "WebPush codec" code could be
contributed back to Netty project,
>>>>>>>> if needed.
>>>>>>>>
>>>>>>>> -Matthias
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Monday, March 30, 2015, Sebastien Blanc
<scm.blanc(a)gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>> I see 2 or 3 differents topics that could be
articulated around
>>>>>>>>> WebPush :
>>>>>>>>>
>>>>>>>>> - Add WebPush support to the UnifiedPush Server
>>>>>>>>> - Create a lightweight Java WebPush Client (think of
embedded
>>>>>>>>> device)
>>>>>>>>> - Create a vert.x mod that implements the WebPush
protocol.
>>>>>>>>>
>>>>>>>>> Sebi
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Mar 30, 2015 at 3:06 PM, Idel Pivnitskiy
<
>>>>>>>>> idel.pivnitskiy(a)gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> I participated in GSoC 2014 with Twitter and
worked on Netty
>>>>>>>>>> last year. Unfortunately, this year Google does
not accept Twitter as a
>>>>>>>>>> mentoring organization. So I'm trying to find
a new organization and a new
>>>>>>>>>> project for this summer.
>>>>>>>>>>
>>>>>>>>>> I know that time for student applications is
over, but I have
>>>>>>>>>> one opened proposal for JBoss Community. I found
WebPush Server at the last
>>>>>>>>>> day of student applications' deadline.
I'm really interested in it and I
>>>>>>>>>> want to change my proposal and work on WebPush
Server!
>>>>>>>>>>
>>>>>>>>>> WebPush Server is a new project which should have
many tasks
>>>>>>>>>> and plan to use new features of Netty 5 (HTTP/2)
and Java 8. All of these
>>>>>>>>>> are very interesting for me. Also I have 2 years
experience of server-side
>>>>>>>>>> development of other services (mobile API,
administrative panels, etc.) on
>>>>>>>>>> Jetty, WildFly and JBoss AS7. So I will be able
to work on any part of
>>>>>>>>>> WebPush Server and not only on server-netty
subproject.
>>>>>>>>>>
>>>>>>>>>> I began to get acquainted with the WebPush Server
code
>>>>>>>>>> base, WebPush Protocol and Push API last weekend.
Also I I've
>>>>>>>>>> used AeroGear UnifiedPush Server in one of my
projects on my work. And it's
>>>>>>>>>> perfect! AeroGear is easy to configure and push
notifications. Thanks to
>>>>>>>>>> all for this work!
>>>>>>>>>>
>>>>>>>>>> Could you, please, help me to find a project idea
for my new
>>>>>>>>>> proposal for WebPush Server?
>>>>>>>>>>
>>>>>>>>>> Best regards,
>>>>>>>>>> Idel Pivnitskiy
>>>>>>>>>> --
>>>>>>>>>> E-mail: Idel.Pivnitskiy(a)gmail.com
>>>>>>>>>> GitHub: @idelpivnitskiy
<
https://github.com/idelpivnitskiy>
>>>>>>>>>> Resume:
>>>>>>>>>>
https://www.dropbox.com/s/q99epi9jyygvaxf/Idel.Pivnitskiy.resume.pdf
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>> aerogear-dev(a)lists.jboss.org
>>>>>>>>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev(a)lists.jboss.org
>>>>>>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev(a)lists.jboss.org
>>>>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev