Heh..point well taken, but do keep in mind, some people actually like the
Model 1 approach better than the Model 2. I used to be one of those people
for many months, until some other developers started adding their own code
to the JSP pages and it didn't conform too well like I had it. Thus..I
realized it was a major pain in the ass to keep track of the changes and
maintain it, especially since JSP scriplet code isn't usually the place
comments are put in (no reason not to..just that it appears that they are
"html" pages with a little bit of code..therefore I have thus far seen
examples of JSP without any comments in it, and have done so myself for the
most part).
> -----Original Message-----
> From: Fyffe Carl [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 05, 2001 12:34 PM
> To: Orion-Interest
> Subject: RE: JSP vs Servlet
>
>
> This was not neccessarily a request for the explaination of
> MVC or CVM or
> VCM or whatever :) Many people learn by example, and this
> example will cause
> newbies to put their code in the JSP if they don't already
> know MVC. I
> think it is up to the more knowledgable folks to lead us less
> knowledgable
> down the correct path, whether they explain all of the
> reasons is up to the
> ammount of time the writers have. This article is VERY good,
> and I learned
> alot from it. Just please be sure you are using "best practices" when
> writing a tutorial. You never know if those little eyes are
> watching :)
>
> --Carl
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Christian Sell
> Sent: Friday, January 05, 2001 3:11 AM
> To: Orion-Interest
> Subject: Re: JSP vs Servlet
>
>
> > Anyway, IMHO adding a methodology on top of the purpose of
> the article -
> > showing the CMP stuff - would have been yet more to learn.
> I'm of the
> > opinion that something like that needs to show off one aspect of the
> > technology rather than all aspects, so MVC - while useful -
> would have
> > been yet another thing to track.
>
> and then he would have had to decide which methodology to
> use. They all
> speak of MVC, but nowadays almost everyone seems to have
> his/her own idea of
> how to implement it. There are so many frameworks out there
> (e.g., Turbine,
> Struts, WebWork, WebMacro, Freemarker, Velocity, to name but
> a few) that it
> is hard to keep track, IMO.
>
>
>
>
