<div dir="ltr">><span style="font-family:arial,sans-serif;font-size:13px">Think "Apache Camel & friends"</span><div><font face="arial, sans-serif">Are we still talking about a "Mobil Gateway" [1] and to have a "no code" solution for developers to use?</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">I've been looking at this previously, and I'm having a hard time to understand who would really use something like this for anything except a simple demo. It would be a different matter if we were going to provided BaaS (Backend as a Service) as we would have more control of the backend and could add features in a reliable way (paging, security etc). </font><span style="font-family:arial,sans-serif">If our Mobil Gateway is simply acting as a intercepting proxy it would be more complicated to add such features, and this added complexity might introduce other issue with regard to connectivity and performance. </span></div>
<div><span style="font-family:arial,sans-serif"><br></span></div><div><span style="font-family:arial,sans-serif">If our goal is to enable enterprise services to be exposed to mobile devices then I think the simplest option for me would be to add a RESTFul interface to those services. This can already be done with Camel, SwitchYard, Vert.x, or by using RestEasy. I would think that a developer tasked with this would want to follow "normal" development practises, using standard development tools, testing, deployment model etc, and not use a web interface perform these task. We could provide all that via the GUI, but my guess would be that developers would choose the standard way just the same. </span></div>
<div><br></div><div><font face="arial, sans-serif">[1] <a href="https://gist.github.com/danbev/717759ef7a445c626f25">https://gist.github.com/danbev/717759ef7a445c626f25</a></font></div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On 11 September 2013 16:50, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
EIP<br>
<br>
to stay cryptic :)<br>
<br>
Thanks Doug for this light.<br>
<br>
++<br>
<span class="HOEnZb"><font color="#888888">Corinne<br>
</font></span><div class="HOEnZb"><div class="h5">On Sep 11, 2013, at 4:40 PM, Douglas Campos <<a href="mailto:qmx@qmx.me">qmx@qmx.me</a>> wrote:<br>
<br>
> On Tue, Sep 10, 2013 at 08:48:48AM +0200, Sebastien Blanc wrote:<br>
>> What does the "integration functionality" exactly stands for ?<br>
><br>
> Think "Apache Camel & friends" :P<br>
><br>
> --<br>
> qmx<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>
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></div></blockquote></div><br></div>