<div dir="ltr">Howdy!<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 15, 2014 at 10:01 AM, Bruno Oliveira <span dir="ltr">&lt;<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>&gt;</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">Good morning,<br>
<br>
Today at our quickstarts, it doesn&#39;t make sense the server[1] without an<br>
interface[2] (I guess).<br></blockquote><div><br></div><div>I think one of the reasons was: RESTful server/interface does not always require a &quot;web-ui&quot;, especially since it was mainly created to serve mobile apps/clients.</div>

<div><br>
</div><div>Instead of throwing the &#39;inherited&#39; web-ui away, there was talks to have it separate. This would also allow one to deployed on a different machine (if there was a need for a web-ui). Dan worked on CORS for that.</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">
<br>
I was just wondering if we could merge both in a single project. Or<br>
maybe make the webapp have the server as dependency, not sure.<br></blockquote><div><br></div><div>If that makes things easier, I am for it - I don&#39;t have a strong feeling on that one.</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">
<br>
Btw the name &quot;client&quot; for the webapp is a little bit odd to me, once it<br>
requires a server.<br></blockquote><div><br></div><div>It&#39;s a client, similar to the mobile apps. The payload posted from both, mobile (e.g. iOS) and the web-app, go eventually against the &#39;backend server&#39; for persistence.</div>

<div>However the deployment environment is slightly different - yes. The iOS demo needs a mobile device as its &#39;container&#39;, while the web-ui needs a JavaEE/Web container.</div>
<div><br></div><div>I think this is very similar to our old [TODO app], which had two WAR files as well. One is &#39;server.war&#39;, the other is the &#39;client.war&#39; (containing the JS and HTML files).</div><div><br>

</div><div>-Matthias<br></div><div><br></div><div>[TODO app] <a href="https://github.com/aerogear/TODO" target="_blank">https://github.com/aerogear/TODO</a></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">


<br>
<br>
[1] -<br>
<a href="https://github.com/aerogear/aerogear-push-quickstarts/tree/master/server/contacts-mobile-picketlink-secured" target="_blank">https://github.com/aerogear/aerogear-push-quickstarts/tree/master/server/contacts-mobile-picketlink-secured</a><br>



<br>
[2] -<br>
<a href="https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/contacts-mobile-webapp" target="_blank">https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/contacts-mobile-webapp</a><br>



<br>
--<br>
<br>
abstractj<br>
PGP: 0x84DC9914<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>