Spray framework has been thoroughly discussed, but I was only able to find surprisingly little about its capabilities to proxy a http request.
In our previous blog post, we introduced the Reactive Orientation Activator template and discussed the server side part of the application which uses Scala, Play framework and some other interesting technologies. In this article, we will focus on the Ember.js, client side of the application.
Ember.js is a single page web application framework. It uses the well known MVC (MVVM) architecture. It utilises handlebars templates as views and two way binding to ensure your HTML stays up-to-date when the underlying model changes and vice versa. Routes are a very important entity in Ember.js and they define state of your application and tie model, view and controller together. The framework favours convention over configuration so naming is very important. Notice that corresponding controller, view and route share the same name (e.g. DeviceController, DeviceRoute). Thanks to robustness, performance and promoting good practices the area where Ember.js really shines are large browser applications that provide real time desktop application feeling. You can find very comprehensive basic tutorials from smashingmagazine or at the official web.