<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 11, 2013 at 2:28 PM, Lucas 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 style="word-wrap:break-word"><br><div><div class="im"><div>On Apr 11, 2013, at 8:07 AM, Kris Borchers <<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>> wrote:</div>
<blockquote type="cite"><div style="word-wrap:break-word"><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div> We would need to build the server side piece into our unified push server</div></div></blockquote><div><br></div><div>yup - that's not hard; it's similar to what we have for iOS and Android; It just uses a different PushNetwork to submit to;</div>
</div></div></div></blockquote><div><br></div>The problem is that push network doesn't exist either and I don't want to wait for the browsers to build them :) … we would need to build that as well. What I am thinking is we would build the network into our server side so that users could deploy their own PushNetwork for their apps but have the ability for the clients to use the appropriate browser PushNetwork if available. Then, we would eventually kill our PushNetwork bits when all browsers implement their own.<br>
</div></div></blockquote><div><br></div></div><div>This could be very cool. Like an enterprise can have their own internal push network</div></div></div></blockquote><div><br></div><div style>I fear that mostly does not work :) You can only send messages to iOS, via APNs; Similar to Android, where it has to go through GCM;</div>
<div style>Providers like Urban Airship, accept the messages (for different networks) and deliver them to APNs, GCM etc </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div><br></div><div><br></div><div>Would this be "built in"( maybe the wrong word) to controller? </div></div></div></blockquote><div><br></div><div style>Not sure what you mean here;</div>
<div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><div class="h5"><div><br></div><br>
<blockquote type="cite"><div style="word-wrap:break-word"><div><blockquote type="cite"><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 style="word-wrap:break-word"> bits but I think the effort would be worth it to provide a cross-browser solution for push on the web which could be transitioned to the native browser push when ready.<br>
</div></blockquote><div><br></div><div><br></div><div>early on ! :)) sounds good!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><div><blockquote type="cite"><div><div dir="ltr"><div>
<h2 style="margin:20px 0px 10px;padding:0px;font-size:24px;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(204,204,204)"><a name="13df912170c16666_13df8ea34079f555_web-push" href="https://gist.github.com/matzew/17f793e4be11473423d2#web-push" style="color:rgb(65,131,196);text-decoration:none;display:block;padding-left:30px" target="_blank"></a>Web Push</h2>
<p style="margin:0px 0px 15px;font-size:13.63636302947998px;font-weight:normal;line-height:20px">The <em>Web Push</em> allows a low-latency message exchange between <em>connected</em> (read: <em>online</em>) clients and the server. This is usually realized with technologies like WebSocket (or robust fallbacks like SockJS). Once a client application connects, it can exchange (receive and send) messages with the server (and other clients). Messages have no restrictions in terms of size of content (JSON, binary). While technoques like SockJS provide a <em>socket connection</em> between the client and the server, it is desired to have a more high-level API, to be used for the communication (e.g. Stomp).</p>
<p style="margin:15px 0px;font-size:13.63636302947998px;font-weight:normal;line-height:20px">Initially, Clients that are offline are <strong>NOT</strong> receiving messages. Messages are not persisted and stored, to be delivered later.</p>
<h3 style="margin:20px 0px 10px;padding:0px;font-size:18px"><a name="13df912170c16666_13df8ea34079f555_supported-client-platforms-1" href="https://gist.github.com/matzew/17f793e4be11473423d2#supported-client-platforms-1" style="color:rgb(65,131,196);text-decoration:none;display:block;padding-left:30px" target="_blank"></a>Supported client platforms</h3>
<ul style="margin-top:15px;margin-right:0px;margin-left:0px;padding:0px 0px 0px 30px;font-size:13.63636302947998px;font-weight:normal;line-height:20px;margin-bottom:0px!important"><li>Android (Java client library)</li><li>
iOS (ObjC client library)</li><li>JavaScript (JS client library, to be used in browsers and hybrid containers)</li></ul><h1 style="font-size:28px;margin:0px 0px 10px;padding:0px;font-family:Helvetica,arial,freesans,clean,sans-serif">
<br></h1><div><span style="font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:14px;line-height:20px">Thoughts? The original gist is store here: </span></div><div><font face="Helvetica, arial, freesans, clean, sans-serif"><span style="font-size:14px;line-height:20px"><a href="https://gist.github.com/matzew/17f793e4be11473423d2" target="_blank">https://gist.github.com/matzew/17f793e4be11473423d2</a></span></font><br>
</div><div><span style="font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:14px;line-height:20px"><br></span></div><div><span style="font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:14px;line-height:20px">-Matthias</span></div>
</div>-- <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>
</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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div><br></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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <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>
</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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div><br></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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div></div></div><br></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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <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>
</div></div>