thx for your comment.
I should better have named my post: “To Zend_MVC or not…”

In fact I had some discussions with people who ask why we do _not_ use the standard Zend Framwork implementation of MVC.

And exactly as you said, what we at Tine 2.0 in MVC, but the Zend Framework interpretation of MVC didn’t fit.

cu
Cornelius

Single Page Application: The pattern was not developed for websites at all, thus it should be quite irrelevant if your website uses a single index.php, a lot of other PHP files, or no PHP at all. As a consequence, using MVC or not is also not related to using a specific programming language or techniques to reach a specific Controller/Action such as rewrite rules.

Service Orientated Architecture: As noted above, MVC was not invented to dynamically create websites. In fact, also GUI applications can greatly benefit from a MVC approach.
What you implemented sounds like a quite normal Model to me (keep in mind that I do not know Tine 2.0 or it’s source code ). If MVC is implemented in a clean way, there is no real need to stick to just one view representation of the same output.

Multi Back-end Capable: This is, again, something which could be a typical requirement for a normal MVC application. Normally, the Controller should have no idea of where the data comes from – it just uses what it gets from the model. And the way this is implemented in the model is then related to the actual backend. Having POPO which have no idea about any type of persistence or backend can also be crucial to stay dynamic.

After all, just knowing Tine 2.0 from your blog post , I think that your implementation of MVC is a pretty standard one, even though it differs from all those PHP frameworks you find on the internet in so far that it sounds better and more dynamic.