I'm trying to get my head around Cappuccino. I'd like my StackOverview peers to review the architecture below and see if it makes sense - the aim is to utilize the unique benefits of Django and Cappuccino without doubling up where the technologies overlap...
When the web browser requests a 'friendly' URL (eg, /, /articles, etc):
- DJango's urls.py matches this to a view.
- The view, rather than doing
DJangos typical work of filling in a
template with the locals dict,
returns the small 'stub' HTML used in a Cappuccino app directly. - The client receives the Cappuccino HTML
- The client requests the Objective J JS URLs mentioned in the stub HTML
- The end-user app is executed and displayed in the browser
The browser now has a working app. When the user does something that requests something from the server:
- The browser sends an XMLHTTPRequest to a URL.
- Django's URLs.py matches this to a view.
- The view does it work, perhaps interacting with the DB model. But instead of returning a template, Django returns some JSON.
- The client recieves the JSON, and does whatever it needs to do.
Does this make sense? We still have the benefit of friendly URLs, and the database being created for us to model our code. However rather than using templates, we're providing Cappuccino stub pages and JSON responses, in order to give users something more like a real app and less like an HTML templating engine.
Is there perhaps a better way of doing things? What do other Pythonistas use? Thanks for your feedback.