<div>
My 2 cents,
</div><div><br></div><div>I was watching that video tonight, is a great approach, assuming that we'll only use app engine for it, already mentioned in this thread.</div><div><br></div><div>So, we're discussing endpoints generation without app engine. We're assuming that our backend will be only Java right? So how could I do the same with torquebox and ruby? Can I generate client source code to ring endpoints on immutant? OpenShift doesn't run only Java, right?</div><div><br></div><div><a href="http://tb-aerogear.rhcloud.com/">http://tb-aerogear.rhcloud.com/</a> <- aerogear + torquebox + ruby</div><div><br></div><div>I would rather to go with well defined endpoints on the server side and build nice APIs to the client side, is just my opinion.</div><div><br></div><div><br></div><div><div><br></div><div><div>-- </div><div>"The measure of a man is what he does with power" - Plato</div><div>-</div><div>@abstractj</div><div>-</div><div>Volenti Nihil Difficile</div></div></div>
<p style="color: #A0A0A8;">On Wednesday, August 15, 2012 at 12:41 PM, Marko Strukelj wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>----- Original Message -----</div><blockquote type="cite"><div><blockquote type="cite"><div><div>If you had some schema describing what you can expect in the</div><div>result, you could use that to generate POJOs and code to</div><div>automatically mashal / unmarshal these. You can also wrap the</div><div>mechanics of HTTP calls away and after done with all that what you</div><div>have is just a class representing a remote service with methods</div><div>taking POJOS that wrap all the mechanics of the remote call and</div><div>return deserialized POJOs back.</div></div></blockquote><div>A point to keep in mind is that code generation should be our</div><div>**last** resort - in a ideal world we have just one client library</div><div>that autodiscovers the rest via a single endpoint.</div></div></blockquote><div><br></div><div>You mean that your javascript module has dependencies specified, and automatically downloads other javascript modules...</div><div>Or you mean that in java client you have a .jar that automatically downloads other jars? Sounds like module system and bootstrap code that harneses the module system to pull down all the code.</div><div><br></div><div>But how does that address hiding plumbing away from the developer? And productivity features like typesafety, and codecompletion that IDEs give you?</div><div>_______________________________________________</div><div>aerogear-dev mailing list</div><div><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></div><div><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>