Yes, HTTP limits the way in which the MVC can be implemented. Using a
java swing client (more Model, View-Controller) - you can have the model inform each observable view when a change has happened. Of course you this is not possible (as far as I know) using HTTP.
Strangely I've recently been using an old legacy database product called Informix 4GL
. This technology is a least 10 years old, not OO, or MVC - but can successfully separates software into different layers. The 4GL forms are a bit like views, the 4GL programs can serve as controllers, and the database as a model.