<div dir="ltr">That means the HTTP endpoints have more the "notion" of an "API server", while the _REAL_ work is dispatched to a message broker<div><br></div><div style>-Matthias</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, May 20, 2013 at 2:20 PM, 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"><div>Hi,</div><div><br></div><div>for ticket "AEROGEAR-1222" ([1]) I looked a bit at JMS integration hooks. The JIRA has an updated description, and two SIMPLE "UML diagrams".</div><div>
<br>
</div><div><br></div><div>Also, I created a branch that uses JMS for (GCM/APNs) based broadcast (more to follow later this week).</div><div><br></div><div>Example:</div><div><br></div><div>The HTTP enpoint for the "broadcast sender", publishes a JMS messages and immediately returns:</div>
<div><a href="https://github.com/matzew/pushee/blob/Messaging/src/main/java/org/aerogear/connectivity/rest/SenderEndpoint.java#L71-L91" target="_blank">https://github.com/matzew/pushee/blob/Messaging/src/main/java/org/aerogear/connectivity/rest/SenderEndpoint.java#L71-L91</a></div>
<div><br></div><div>Yes, there is no guarantee at all, that the message really arrives the device (see Apple/GCM doc for details)</div><div><br></div><div>Behind the sceneses, a "Consumer" is responsible to deliver the message to the network:</div>
<div><a href="https://github.com/matzew/pushee/blob/Messaging/src/main/java/org/aerogear/connectivity/jms/sender/GlobalPushNotificationSenderListener.java#L46-L58" target="_blank">https://github.com/matzew/pushee/blob/Messaging/src/main/java/org/aerogear/connectivity/jms/sender/GlobalPushNotificationSenderListener.java#L46-L58</a></div>
<div><br></div><div>The code above performs all the "heavy" work ("blocking" JPA lookups and PushNEtwork Delivery).. </div><div><br></div><div><br></div><div>We now should use the "standalone-full.xml" configuration, since that supports JMS. I double checked and the SimplePush/Netty Adapter are working fine here too.... also, for JMS (for now), we need to declare some JMS topics in the "standalone-full.xml" file</div>
<div><br></div><div>More during the week,</div><div><br></div><div>Matthias</div><div><br></div><div>[1] <a href="http://jira.jboss.org/browse/AEROGEAR-1222" target="_blank">http://jira.jboss.org/browse/AEROGEAR-1222</a></div>
<span class="HOEnZb"><font color="#888888"><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>
</font></span></div>
</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>