We have a web2py
application that we want to connect to an EmberJS
client. The idea is to use the responsive capabilities of EmberJS
to keep the client updated writing minimal code.
We have (REST
) primitives which are in charge of creating / updating the underlying datastore (CouchDB
). These primitives are sometimes complex and covering corner cases, involving the creation of several documents, connecting them, validating configuration parameters, ... This is implemented in the backend. We would like to avoid duplicating the full modelling of the data in our EmberJS
application, and avoid duplicating the logic implemented by those primitives.
I have some questions:
- does it make sense in
EmberJS
to just model a subset of the data in the documents? We would just create models for the small amount of properties that the user is able to interact with. The client would not see the fullCouchDB
documents, just the data necessary for display / interaction. - is it possible to connect
EmberJS
to aREST
interface, without having to fully model the underlying data in the database?