Thx for clarification. It was not just about the server side. They have also nice wrappers on the clientside. ;)<div class="gmail_extra"><br><br><div class="gmail_quote">2012/12/18 Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Dec 18, 2012 at 12:46 PM, Daniel Manzke<br>
<<a href="mailto:daniel.manzke@googlemail.com">daniel.manzke@googlemail.com</a>> wrote:<br>
> nothing to do with your case, but just my two cents. don't invent another<br>
> library to wrap it up. use atmosphere instead ;)<br>
<br>
</div>well, main focus here is offering client APIs and client functionality.<br>
<br>
On the server side there will be just a light/tiny/thin layer around<br>
an _existing_ WebSocket server. Most-likely JSR 356 implementation.<br>
If Atmosphere comes with an impl of that (I think the want to do<br>
that), it could be used. Or what ever the underlying container uses.<br>
<br>
Similar to our REST "extensions"<br>
<br>
Also, outside of the JavaEE realm, we wanna make sure that things like<br>
Netty (read: protocol servers) can be hooked in as well.<br>
<br>
Don't worry, nobody is writing yet another WebSocket server here<br>
<br>
Cheers!<br>
Matthias<br>
<br>
[1]<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
><br>
> 2012/12/17 Jay Balunas <<a href="mailto:jbalunas@redhat.com">jbalunas@redhat.com</a>><br>
>><br>
>><br>
>> On Dec 17, 2012, at 3:08 PM, Matthias Wessendorf wrote:<br>
>><br>
>> > On Mon, Dec 17, 2012 at 9:04 PM, Jay Balunas <<a href="mailto:jbalunas@redhat.com">jbalunas@redhat.com</a>><br>
>> > wrote:<br>
>> >> This is similar to what I was thinking as well.<br>
>> >><br>
>> >> There are two main types of push; native & non-native, but I don't like<br>
>> >> those designations. It is really more like "live" & "background" push,<br>
>> >> referring to the state of the client.<br>
>> >><br>
>> >> Live push == Application is open, and active on the client. Push msgs<br>
>> >> are routed to the application via more traditional long/short polling,<br>
>> >> websockets, etc...<br>
>> >><br>
>> >> Background push == Application is closed, and not active on the client.<br>
>> >> Regular live push messages are not possible. The only way to communicate is<br>
>> >> via APN, GC native messaging (sorry web apps - no love).<br>
>> >><br>
>> >> In an ideal world there would be no difference to the application<br>
>> >> developer using AeroGear API's (client or server). The server-side would<br>
>> >> know what clients are available, and the clients would be listening<br>
>> >> automatically. Sending a message would be agnostic for the server-side.<br>
>> >><br>
>> >> Unfortunately this can not "fully" be the case as background/native<br>
>> >> messages have limitations on the content, client support, and delivery<br>
>> >> mechanisms.<br>
>> ><br>
>> > one option is, to "push / poll". The client gets a msg on what to<br>
>> > fetch. When back online it performs a "normal" fetch/poll for the data<br>
>> > in question<br>
>><br>
>> +1 - I've seen that sort of thing as an option for native push - its<br>
>> really just a phone call to tell the app it has an email - go read it :-)<br>
>><br>
>> ><br>
>> >> So I think the best we can do is setup a "smart" message system that<br>
>> >> gets you pretty close with good fallback api's and checks for what sort of<br>
>> >> messages are possible, or configured.<br>
>> >><br>
>> >> Make sense, or is this just a big ramble? :-)<br>
>> >><br>
>> >> -Jay<br>
>> >><br>
>> >> On Dec 5, 2012, at 2:14 AM, Matthias Wessendorf wrote:<br>
>> >><br>
>> >>> well,<br>
>> >>><br>
>> >>> the idea is to have a wrapper/hook for "push notification" (e.g. APN)<br>
>> >>> in the notifier as well:<br>
>> >>> * receiving 'native push' events, when the app is offline (inactive,<br>
>> >>> not watching the tab/window)<br>
>> >>><br>
>> >>> If an app is offline, you simple can't receive a websocket frame/msg.<br>
>> >>> So push is needed to tell AG that is needs to fetch data for sync etc.<br>
>> >>><br>
>> >>> -Matthias<br>
>> >>><br>
>> >>> On Mon, Dec 3, 2012 at 4:51 PM, Burr Sutter <<a href="mailto:bsutter@redhat.com">bsutter@redhat.com</a>><br>
>> >>> wrote:<br>
>> >>>> I am concerned about the words "push" and "notifier" as those can<br>
>> >>>> become confused with real "push notifications" which we will have to have a<br>
>> >>>> client API for in the future.<br>
>> >>>><br>
>> >>>><br>
>> >>>> On Dec 3, 2012, at 2:46 AM, Matthias Wessendorf wrote:<br>
>> >>>><br>
>> >>>>> any further comments?<br>
>> >>>>><br>
>> >>>>> On Thu, Nov 22, 2012 at 9:51 AM, Matthias Wessendorf<br>
>> >>>>> <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>> >>>>>> Hi,<br>
>> >>>>>><br>
>> >>>>>> yesterday some folks of the team meet, to talk about WebSocket -<br>
>> >>>>>> more<br>
>> >>>>>> generally (HTML5) connectivity.<br>
>> >>>>>><br>
>> >>>>>> Here is a write-up from the meeting:<br>
>> >>>>>> <a href="https://gist.github.com/dd6e3c2da08830776996" target="_blank">https://gist.github.com/dd6e3c2da08830776996</a><br>
>> >>>>>><br>
>> >>>>>> Feedback and comments are welcome - Please use the comment function<br>
>> >>>>>> on<br>
>> >>>>>> that gist!<br>
>> >>>>>><br>
>> >>>>>> Cheers!<br>
>> >>>>>> Matthias<br>
>> >>>>>><br>
>> >>>>>> --<br>
>> >>>>>> 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><br>
>> >>>>><br>
>> >>>>><br>
>> >>>>><br>
>> >>>>> --<br>
>> >>>>> 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><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>
>> >>>><br>
>> >>>><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>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> --<br>
>> >>> 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><br>
>> >><br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > 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><br>
>><br>
>><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>
><br>
><br>
><br>
><br>
> --<br>
> Viele Grüße/Best Regards<br>
><br>
> Daniel Manzke<br>
<br>
<br>
<br>
--<br>
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><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Viele Grüße/Best Regards<br><br>Daniel Manzke<br>
</div>