On Wed, 01 Oct 2008 18:09:20 +0200, Bruno Desthuilliers wrote: > Phillip B Oldham a écrit : >> On Oct 1, 4:12 pm, Thomas Guettler <[EMAIL PROTECTED]> wrote: >>> Please explain what you want to do. >> >> I'm primarily looking for alternatives to MVC frameworks for web >> development, particularly SAAS. I've looked around, and some >> whitepapers suggest that event-based frameworks often perform better >> than MVC. Since I'm looking at SAAS, having a "view" is pretty >> pointless since I'll either be using Thrift, returning simple HTTP >> headers, or returning some sort of JSON/YAML/XML content (possibly >> based on accept headers). > > "view" doesn't imply (x)html - any valid HTTP response is ok. The whole > point of decoupling controler from view (in web MVC) is to allow the > same controler to return different views.
In fact, MVC and event-driven is two entirely different concept. You can have both, or none. It is, in the end, your choice which one to use or whether you want to use both or none. Event-driven programming is a concept that your programs are entirely composed of function definition and binding that function definition to events. The rest is handled by a mainloop, which calls the appropriate functions when it receives something. MVC is a separation of concern. In MVC code you want that there is a clear boundary between code that handles Model, View, and Controller, so it'd be easier to manage the code. -- http://mail.python.org/mailman/listinfo/python-list
