 |
 |
 |
 |
To: turbine@list.working-dogs.com
Subject: Re: Is Turbine MVC or HMVC?
Date: Wed, 11 Oct 2000 14:04:52 +0200
From: Christoph Reck Christoph.Reck@dlr.de
|
 |
 |
 |
 |
Turbine follows the MVC desing pattern.
- Model - the underlying data sources (via peers or beans)
- View - one of the templating engines
- Controller - Turbine servlet plus your action+screen classes
Since the view and the controller are tightly coupled in Turbine,
it is stated to follow the Model2 design pattern, with a + 1
addition due to way actions are used (hence Model 2 + 1).
Turbine does not directly support the Hierachical MVC pattern, but
it cout be used this way by defining multiple module and template
pathes (would impact performance). Note that in the HMVC each MVC
instance is self-contained and separable from the rest.
Note that many components within a MVC system follow themselves
the MVC pattern, therefore most MVC systems are also HMVC systems
(this also applies to Turbine as a whole, but your application with
Turbine is normally not HMVC).
Also note that you could use Turbine in a non MVC manner, but
normally it leads you to use it as MVC (which JSP does not).
I hope this clarifies your question,
Christoph