<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 27, 2013 at 5:51 PM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</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"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Mon, May 27, 2013 at 8:09 AM, 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div>On Sun, May 26, 2013 at 6:45 AM, Douglas Campos <span dir="ltr"><<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>On Thu, May 23, 2013 at 02:28:47PM -0400, Jay Balunas wrote:<br>
> One question that came up around the JMS stuff is how will it work on<br>
> top of plain old Tomcat? Will we be including the extra libs for that<br>
> case? Or perhaps that functionality is only available if JMS is part<br>
> of the container?<br>
</div>That's exactly why I was unhappy with this change =/<br></blockquote><div><br></div></div><div>fair point, right now JMS is not used for much.</div><div><br></div><div>Once a request hits the server (e.g. request against our HTTP sender API), we produce a JMS message and send a "JOB Submitted" 200 HTTP request.</div>
<div>The consumer for the JMS message does all the work that _may_ take longer, and is blocking IO (->JPA).</div><div>E.g. it looks up the MobileVariantInances and is responsible for delivering the messages to the actual push networks (GCM/APNs).</div>
<div><br></div><div>I think, that we can remove the JMS part, at least for now. (e.g. for the early August release). However, I am sure, that at some point messaging will helpful for scaling/throughput.</div><div>
<br></div><div>For now, we could use CDI events in combination with the @Asynchronous EJB annotation (for publishing and receiving).</div></div></div></div></blockquote><div><br></div></div><div>Maybe I'm totally wrong but using EJB on a plain old Tomcat/Jetty will be the same issue as using JMS, no ? (Or by Tomcat when meant TomEE ? )</div>
</div></div></div></blockquote><div><br></div><div style>JMS integration is a bit harder (separated broker), compared to deploying an embedded EJB container (e.g. Apache OpenEJB).</div><div style>I have always thought that we do target - first - the WebProfile of JavaEE 6 (which contains EJB, but not JMS)<br>
</div><div style><br></div><div style>-Matthias</div><div style><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 dir="ltr"><div class="gmail_extra">
<div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><br></div><div>would that be OK ?</div><span><font color="#888888"><div><br></div>
<div>-M</div></font></span><div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span><font color="#888888"><br>
--<br>
qmx<br>
</font></span><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><br>
</div></div></blockquote></div></div><br><br clear="all"><div><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></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></div><br></div></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>