What are the risks of described approach to developing web application?
<p>We want to write a UI that consists of HTML, Javascript (JQuery) and CSS. Although the initial starting point will be served up by a web server, there won't be any sever side templating. The browser will interact with the server via a restful interface and render its UI.</p>

<p>What are the risks of this approach? </p>

<p>Ideally I'd like a nice, straightforward javascript OO api which underneath makes http calls to the server to get JSON representations of resources.  Any suggestions as to how this could be structured?</p>

<p>Anyone have experience with browser side templating? </p>

<p>Is there a framework to make this style of development easier? </p>

<p>We will also be defining the server side resources and my thoughts are to follow ruby on rails conventions. For example, if you define a Users resource in routes.rb, you have 7 uri templates. Any thoughts?</p>

<p>By the way, the server side functionality will be developed in java.</p>
