Side note:
the document betweens <<'s and >>'s is called model2.xml
Didier.
Didier Dubois wrote:
>
> Jon Stevens wrote:
> >
> > on 10/11/2000 5:28 AM, "Didier Dubois" <[EMAIL PROTECTED]> wrote:
> >
> > > Excellent!
> > > That indeed clarify everything and I think it the most clear + concise
> > > explaination I've ever read about that.
> > >
> > > Why not put your text somewhere on the Turbine page or in some FAQ page?
> >
> > SEND A PATCH. :-)
> >
> > -jon
>
> here it is. But I don't feel happy with the mail formatting.
> Didier.
>
> Index: site-book.xml
> ===================================================================
> RCS file: /products/cvs/turbine/turbine/xdocs/site-book.xml,v
> retrieving revision 1.6
> diff -c -r1.6 site-book.xml
> *** site-book.xml 2000/09/29 22:07:38 1.6
> --- site-book.xml 2000/10/12 08:56:37
> ***************
> *** 26,30 ****
> --- 26,32 ----
> <page id="oracle-howto" label="Oracle 8i Howto"
> source="oracle-howto.xml"/>
> <page id="hypersonic-howto" label="HypersonicSQL Howto"
> source="hypersonic-howto.xml"/>
> <separator/>
> + <page id="model2" label="What is the Model 2+1?"
> source="model2.xml"/>
> + <separator/>
> <page id="summit" label="Turbine Summit" source="summit.xml"/>
> </book>
>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> <?xml version="1.0"?>
>
> <document>
>
> <header>
> <title>Turbine Model 2+1</title>
> <subtitle>Turbine Model 2+1</subtitle>
> <authors>
> <person name="Turbine Documentation Team" email="[EMAIL PROTECTED]"/>
> </authors>
> </header>
>
> <body>
>
> <s1 title="What is model 2+1?">
> <p> From the mail of Christop Reck: </p>
> <p> Subject: Re: Is Turbine MVC or HMVC?</p>
> <p> Date: Wed, 11 Oct 2000 14:04:52 +0200</p>
> <p> From: Christoph Reck [EMAIL PROTECTED]</p>
>
> <p>
> Turbine follows the MVC desing pattern.
> </p>
> <p>
> <ul>
> <li> Model - the underlying data sources (via peers or beans)</li>
> <li> View - one of the templating engines</li>
> <li> Controller - turbine servlet plus your action+screen classes</li>
>
> </ul>
> </p>
> <p>
> 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).
>
> </p>
> <p>
> 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.
>
> </p>
> <p>
> 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).
>
> </p>
> <p>
> 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).
>
> </p>
> <p>
> I hope this clarifies your question,
> Christoph
> </p>
> </s1>
> <s1 title="Resources">
>
> <p>
> <link
>
>href="http://www.javaworld.com/javaworld/jw-12-1999/jw-12-ssj-jspmvc.html">Understanding
> JavaServer Pages Model 2 architecture</link>
> </p>
>
> </s1>
> </body>
> </document>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> --
> mailto:[EMAIL PROTECTED] http://www.idbsoft.ch
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
--
mailto:[EMAIL PROTECTED] http://www.idbsoft.ch
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
