I think I've eaten some stupid soup today. Could someone explain to me what the backend is all about? As far as I see it, the command line creates a backbone template and syncs it with the server. Which is dandy, but as it's client code anyway, that's mostly static web hosting.
So now I'm ready to create a hyper-nifty Web 2.71 interface to WHOIS. So normally I'd create a simple web app that serves me my data. Where does backlift come in here, as I'm not doing CRUD all from within the app itself?
Whenever you persist data to a backend, say by calling save() on a model, it seems Backlift will handle the backend for you, that is, it gives you a server to process the PUT request and a place to store the data. Then to retrieve the data on the front end, you just do a fetch().
So now you just do save() and fetch() and you never worry about what happens in between.
So now I'm ready to create a hyper-nifty Web 2.71 interface to WHOIS. So normally I'd create a simple web app that serves me my data. Where does backlift come in here, as I'm not doing CRUD all from within the app itself?