I was considering building an admin that would consist of two components, a 
totally separate HTML/CSS/JS frontend that presumed API endpoints, and a 
backend written in Tornado (similar to Flask in a lot of ways) that caught all 
of the presumed endpoints and performed the db operations.  The idea of 
separating them is to make the frontend portable across backends so that a 
backend could be written in Tornado/Flask/Django/RoR(*shudder*)/whatever you 
want as long as it followed the conventions leading to the API endpoints.  I've 
seen a couple backends out there but haven't been too happy with any of them, 
and I haven't found any doing something like this.
-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to