First of all ember is great I will use it. But there is one point I feel very uncomfortable with....
Embers url pattern to add delete, edit or create objects. In my opinion they are not restful.
The ember way is a little bit like the soap way. And the soap way handling methods is not the restful way of the WEB
In Ember you define a resource and routes on this resource.
@resource "order", ->
@route "edit"
@route "new"
etc.
For example someServer/orders/new does not represent a resource in the restful way. It represents an action on the resource in this case orders.
In the restful way CRUD is done via http verbs and not with explicit semantic action expressions in the url.
In my opinion there is a missfit between the ember way of routing as absolute state and the way web works.
A single page application does not need any http verbs (it does not talk to the server for a longer period of time) except when synchronizing with the server. But from the absolute point of view (A user does not know wether it is a single page app or many pages with request responses) there must be something else for the http verbs. But what ?
If there is a semantic in the url and not only state : Does bookmarking of the delete action of a resource make sense ? Is it (REST)web conform ?
Lets think a little bit more far: Suppose ember would also run on the server (just think very modular - no output no templates - just logic) . Then a delete of a record is not done with one of the http verbs but done with an explicit call of a method. Then You do not need any http verbs just posts like soap right ?
I have tried to implement a restful way in my emberplayground at github. All methods are in the controller, from there the view are triggered.
Perhaps there are other problems with this solution but the url does not show any semantic methods like edit or new.
https://github.com/erhard/emb_boot/tree/controlleractions
