Just noticed this. Agreed, although I think we may be working from different definitions of MVC. I read it as a broad (but still useful) term describing a clas

Just noticed this. Agreed, although I think we may be working from different definitions of MVC. I read it as a broad (but still useful) term describing a class of related architectural patterns designed to decouple presentational logic from domain logic. While I've heard different people describe different (related) kinds of architectures as MVC, I've not actually encountered that much religious debate about which is the "one true" definition. So I'm not sure exactly which MVC variant is the one that you're reacting against as the dogmatic "pure" one. You're more-or-less right about my client-server architecture - I have a split model, and my V and C are somewhat mixed. As the unit of reuse (outside the model) is the Widget, there's quite a fluid spectrum between "view-y" widgets and "controller-y" widgets, meaning you can make a decision based on the individual merits of the situation on how far to split the two. But still have a useful framework in which to do so. It's my favourite kind of MVC, but perhaps need a more specific name for it!