<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 12, 2013 at 2:34 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I couldn't agree more with you Dan and I think that "Camel & Friends"<br>
was supposed to be done by the team responsible for it, in other worlds<br>
Camel team.<br>
<br>
To me is clear as crystal that our job is to improve the experience with<br>
mobile like we did with SimplePush, UnifiedPush...etc.<br></blockquote><div><br></div><div>yeah, same feelings here;</div><div><br></div><div>I think the integration with "Camel & Friends" came up, during the Face2Face, when looking for UP/SP integration w/ the controller</div>
<div>(I guess that's when Camel integration for the controller came up as well (or was shown)</div><div><br></div><div>-M</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
We are not an integration platform as far as I know. (I can be wrong)<br>
<br>
> Daniel Bevenius <mailto:<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>><br>
> September 12, 2013 2:30 AM<br>
<div class="im">> >Think "Apache Camel & friends"<br>
> Are we still talking about a "Mobil Gateway" [1] and to have a "no<br>
> code" solution for developers to use?<br>
><br>
> I've been looking at this previously, and I'm having a hard time to<br>
> understand who would really use something like this for anything<br>
> except a simple demo. It would be a different matter if we were going<br>
> to provided BaaS (Backend as a Service) as we would have more control<br>
> of the backend and could add features in a reliable way (paging,<br>
> security etc). If our Mobil Gateway is simply acting as a intercepting<br>
> proxy it would be more complicated to add such features, and this<br>
> added complexity might introduce other issue with regard to<br>
> connectivity and performance.<br>
><br>
> If our goal is to enable enterprise services to be exposed to mobile<br>
> devices then I think the simplest option for me would be to add a<br>
> RESTFul interface to those services. This can already be done with<br>
> Camel, SwitchYard, Vert.x, or by using RestEasy. I would think that a<br>
> developer tasked with this would want to follow "normal" development<br>
> practises, using standard development tools, testing, deployment model<br>
> etc, and not use a web interface perform these task. We could provide<br>
> all that via the GUI, but my guess would be that developers would<br>
> choose the standard way just the same.<br>
><br>
> [1] <a href="https://gist.github.com/danbev/717759ef7a445c626f25" target="_blank">https://gist.github.com/danbev/717759ef7a445c626f25</a><br>
><br>
><br>
><br>
</div><div class="im">> _______________________________________________<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>
</div>> Corinne Krych <mailto:<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>><br>
> September 11, 2013 11:50 AM<br>
<div class="im">> EIP<br>
><br>
> to stay cryptic :)<br>
><br>
> Thanks Doug for this light.<br>
><br>
> ++<br>
> Corinne<br>
><br>
</div><div class="im">> _______________________________________________<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>
</div>> Douglas Campos <mailto:<a href="mailto:qmx@qmx.me">qmx@qmx.me</a>><br>
> September 11, 2013 11:40 AM<br>
<div class="im">><br>
> Think "Apache Camel & friends" :P<br>
><br>
</div>> Sebastien Blanc <mailto:<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>><br>
> September 10, 2013 3:48 AM<br>
<div class="im">> What does the "integration functionality" exactly stands for ?<br>
><br>
><br>
><br>
><br>
</div><div class="im">> _______________________________________________<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>
</div>> Douglas Campos <mailto:<a href="mailto:qmx@qmx.me">qmx@qmx.me</a>><br>
> September 10, 2013 2:01 AM<br>
<div class="im HOEnZb">> Howdy!<br>
><br>
> According to yesterday's team meeting, we need to update our Grand<br>
> RoadMap[1].<br>
><br>
> Things to note:<br>
><br>
> - We know the schedule will slip, because push - we just need to<br>
> estimate accordingly.<br>
> - IMHO Security will need a little bit more room than the aggressive<br>
> 6-week cycle - my shoot is 8-week minimum.<br>
> - What about the showcase app? Does it have more priority than the<br>
> "integration functionality?"<br>
> - Offline/Sync: To do it together or not, that's the question!<br>
><br>
> Let's discuss this RoadMap during this week so we can just agree on the<br>
> outcome at our next team's meeting, **next monday**. I know timing is<br>
> tight but Jay needs this...<br>
><br>
> Thanks y'all!<br>
><br>
> [1]:<a href="https://github.com/aerogear/aerogear.org/blob/master/docs/scratchpad/AeroGear20RoadMap.markdown" target="_blank">https://github.com/aerogear/aerogear.org/blob/master/docs/scratchpad/AeroGear20RoadMap.markdown</a><br>
><br>
</div><div class="HOEnZb"><div class="h5">> _______________________________________________<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>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
abstractj<br>
<br>
<br>
</font></span><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>