Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
what’s left to do for a backend framework in order to provide a restful service to a frontend application based on backbone.js or other full MVC frontend framework?
I can think of
what else?
A few additional things (though any could probably be considered parts of things you’ve already mentioned in the question):
Acting as an intermediary
As long as we have domain restrictions on Ajax, it will be necessary to offer a proxy to enable mashups. Even once we fix that problem, though, there are other cases for an intermediary. Take, for example, Twitter’s streaming API. Twitter only allows one stream per API key, so your backend app will have to be the consumer that then sends search results to the clients.
Search
Bandwidth and client processing capabilities both limit the degree to which search can be done on the client.
Jobs
Background or batch job processing is often best done on the server. A good RESTful practice is to
POSTto/jobs, get a202 Acceptedwith aContent-Locationheader pointing to the running job. Subsequents to that job return a status and, if it’s complete, a link to the results.